GET /time/{timezone}

Time API

Local time for your app. One instant across every timezone.

Try it

Use this request in your app

1M requests · $20/mo.

Get started

Start with what you have.

An airport on an itinerary. A city in a booking. An IP from a visitor. Turn the place you already have into the local time you need.

Example airport lookup · September 24, 2026

Airport code

JFK

John F. Kennedy International

New York

UTC-04:00

Sep 24, 2026

Cities and countries can have more than one answer. Get the choices and let your app ask. Unknown locations stay unknown.

Also accepts coordinates, ICAO airport codes, recorded port UN/LOCODEs and matched US street addresses. IP results follow network-location evidence.

Explore location inputs

One meeting.
Everyone’s local time.

Set a meeting in New York. Show its local date and time in up to ten destinations, even when it’s tomorrow in Tokyo.

Example conversion · August 29, 2026

New York

UTC-04:00

Aug 29, 2026

London

UTC+01:00

Aug 29, 2026

Tokyo

UTC+09:00

Aug 30, 2026

One request. The same Unix timestamp.See the request

When 1:30 happens twice.
Choose the one you mean.

Clocks change. Your app can choose the first or second occurrence, or ask for clarification. A skipped time can be rejected or shifted.

New York · November 1, 2026 · Clocks move back one hour

  1. First occurrence

    UTC-04:00

  2. Second occurrence

    UTC-05:00

See when the seasonal clock changes start and end, with local time on both sides. Standard offsets and seasonal adjustments stay separate.

Choose how clock changes resolve

Building a timezone picker? Filter by country, offset or daylight saving. Turn an abbreviation into explicit choices. Get the timezone catalog.

From this page to your app.

Copy a working request. Use an SDK in your language, or give your agent Time through MCP. One key connects them all.

curl "https://api.parseapi.com/time/America%2FNew_York?at=2026-08-29T19%3A00%3A00Z&deep=true" \
  -H "X-API-Key: YOUR_API_KEY"
{
  "timezone": "America/New_York",
  "abbreviation": "EDT",
  "offset": "-04:00",
  "dst": true,
  "at": "2026-08-29T15:00:00-04:00",
  "unix": 1788030000,
  
    "name": "Eastern Time",
    "offset_minutes": -240,
    "offset_seconds": -14400,
    
      "at": "2026-11-01T06:00:00.000Z",
      "dst": false,
      "offset": "-05:00",
      "abbreviation": "EST"
    },
    "resolution": null
  }
}

API referenceSDKsMCP for agentsKeys and authentication

Every response field

Response fields

latitudenumber or null
Input or resolved location latitude. Null if there is no single coordinate; omitted for timezone-only requests
longitudenumber or null
Input or resolved location longitude. Null if there is no single coordinate; omitted for timezone-only requests
timezonestring or null
IANA timezone id. Nautical Etc/GMT zone over open ocean
abbreviationstring or null
Timezone-rule abbreviation, such as EDT or JST; some zones use numeric labels. Not a unique timezone identifier
offsetstring or null
UTC offset as ±HH:MM. Historical subminute offsets include :SS
dstboolean or null
Daylight-saving indicator from the timezone rules at the reference time, including negative seasonal adjustments
atstring or null
Local date and time as ISO 8601 with the resolved UTC offset. Always present; now unless ?at= selects a moment. Null for an ambiguous or unresolved source location
toobject or null
With ?to= only: the other zone evaluated at the same instant
unixinteger or null
Unix timestamp in seconds for the resolved instant. Always present; fractional seconds round down. Null for an ambiguous or unresolved source location
to.atstring
The converted local date and time, ISO with its UTC offset
to.unixinteger
The same Unix timestamp as unix: both zones describe one instant
targetsarray or null
With targets= instead of to=: ordered array of 1–10 destination clocks, each with timezone, at, unix, offset, abbreviation and dst. Duplicates stay in place; every unix matches the source. Null if the source location is ambiguous or unresolved
locationobject
For explicit place inputs: input, status (resolved, ambiguous or not_found), candidates and truncated. Ambiguous/missing locations retain null clock fields. Choose a candidate timezone explicitly

Deep fields

deep.namestring or null
Friendly / generic name (e.g. Eastern Time)
deep.offset_minutesinteger or null
UTC offset in whole minutes, truncated toward zero
deep.offset_secondsinteger or null
Exact UTC offset in seconds, including historical subminute offsets
deep.next_dstobject or null
Next offset transition after the reference time, or null
targets[].deepobject
With deep=true: name, offset_minutes and offset_seconds for this destination
deep.resolutionobject or null
For offsetless conversion: kind (unique, overlap or gap), applied policy, signed adjustment_seconds, and earlier/later alternatives with at, unix and offset. Unique times have an empty alternatives array. Null for now, explicit offsets, no destination or an unresolved source location
deep.standard_offsetstring or null
Standard UTC offset at the requested instant, as ±HH:MM[:SS]. Null when unresolved
deep.standard_offset_secondsinteger or null
Exact standard UTC offset in seconds, from the same timezone rules
deep.dst_offset_secondsinteger or null
Actual offset minus standard offset, in seconds. Preserves zero, negative saving and double daylight saving
deep.seasonobject or null
Current DST-flag interval, or next interval starting within 400 days. start and end each contain the UTC boundary, before/after local clocks and change_seconds; each boundary can independently be null. Null when no interval is known

Build with Time

All tutorials →

QUESTIONS

How do I get the current time?

GET /time returns UTC now. Use /time/America/New_York for a local clock. The response includes the date and time with its UTC offset, plus the same instant as Unix seconds.

Can I convert a time for my whole team?

Yes. Add to= for one destination, or targets=Europe/London,Asia/Tokyo for up to ten. Set at= for a particular time, or leave it out for now. Every destination describes the same instant in the order you requested.

What happens when clocks change?

The API defaults to the first occurrence of a repeated time and moves a skipped time forward by the clock gap. Use disambiguation=reject to return an error instead, or earlier/later to choose a result. The converter above asks you to choose.

Can I check a past or future time?

Yes. Pass at= with an ISO timestamp. Z or a UTC offset identifies one instant. Without an offset, conversions read the time in the source zone; other lookups read it as UTC. Future answers follow the available rules and may change when those rules change.

How do I find the right timezone?

Start typing an IANA identifier in the demo. In your app, search /time/zones or filter by country, area, UTC offset and daylight saving. Add details=true for picker labels and sort=offset to order them. An abbreviation such as CST returns all matching identifiers so you can choose explicitly.

Can I start with a city, airport or IP?

Yes. The Place tab accepts city names, countries, IATA and ICAO airport codes, port UN/LOCODEs, IP addresses, and recorded US address points. Add country and state context to narrow a city. Multiple matches return choices; unknown locations keep the clock unresolved.

Can I use coordinates?

Yes. Pass lat and lon to get the timezone and local time at a point. Fractional-hour offsets work too, including India and Nepal. Open ocean uses nautical timezones; their normal UTC offset is included in the answer.

Is optional detail included on Free?

A lookup or conversion to up to ten destinations uses one pooled request on every plan. New accounts need a paid plan for optional Deep; existing accounts keep their current access. Deep includes standard and seasonal offsets, the next clock change, seasonal start/end clocks, the rules edition, and how a local wall time was resolved.

Find local time by ZIP with timezone by ZIP, or plan across zones with the time zone converter.