Skip to content
    TimeLogic API logoTimeLogic API
    Sign in
    All guides

    Bulk time and timezone API guide

    Resolve or convert multiple timezone targets in one request while preserving input order.

    When should I use bulk mode?

    Use the bulk timezone API or bulk time conversion API when one operation needs several timezone, IP, or fixed-offset targets. /v1/time/current and /v1/time/convert accept a comma-separated list in one selector family and return an array in input order. Resolve city, country, or IP locations first when your application needs those selectors.

    curl "https://api.timelogicapi.com/v1/time/current?tz=Europe/Paris,Asia/Tokyo,America/New_York" \
  -H "Authorization: Bearer $TIMELOGIC_API_KEY"

    Request patterns

    Current time with several named zones:

    GET /v1/time/current?tz=Europe/Paris,Asia/Tokyo,America/New_York

    Conversion to several offsets:

    GET /v1/time/convert?unix=1711300000&offset=-04:00,%2B00:00,%2B09:00

    The input order is preserved in the response array, which lets a caller pair each result with the original selector without guessing how the service sorted the values.

    Rules and trade-offs

    • Keep all values in one selector family. tz=a&ip=b is ambiguous and is rejected.
    • Use one timestamp input for bulk conversion; every returned item represents that same instant.
    • URL-encode a plus sign in fixed offsets as %2B.
    • /v1/time/clock is single-target only, so use the JSON endpoints for bulk work.
    • Keep the API key server-side even when the results are rendered in a browser application.

    See bulk mode documentation, current time, and time conversion.