GET /time/{timezone}
Time API
One instant. Every local time.
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.
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.
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.
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.
First occurrence
UTC-04:00
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.
Building a timezone picker? Filter by country, offset or daylight saving. Turn an abbreviation into explicit choices. Get the timezone catalog.
Coverage
IANA timezones. Land and ocean.
Start with a timezone, a city, an airport or an IP. Get its local clock, then convert one moment across your team. See both sides of seasonal clock changes. One request, including optional detail, on every plan.
SPEED
How long /time takes.
Median time to first byte over the last seven days. Warm requests, measured every 30 minutes. Live verification and other request variants can take longer.
US
41ms
EU
35ms
APAC
48ms
LatAm
46ms
ME
105ms
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:00:00Z" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Parse-Version: 2.0.0"// Example response · 200{"timezone": "America/New_York", "abbreviation": "EDT", "offset": "-04:00", "dst": true, "at": "2026-08-29T15:00:00-04:00", "unix": 1788030000 }
API referenceSDKsMCP for agentsKeys and authentication
Every response field
Response fields
- latitude
- Input or resolved location latitude. Null if there is no single coordinate; omitted for timezone-only requests
- longitude
- Input or resolved location longitude. Null if there is no single coordinate; omitted for timezone-only requests
- timezone
- IANA timezone id. Nautical Etc/GMT zone over open ocean
- abbreviation
- Timezone-rule abbreviation, such as EDT or JST; some zones use numeric labels. Not a unique timezone identifier
- offset
- UTC offset as ±HH:MM. Historical subminute offsets include :SS
- dst
- Daylight-saving indicator from the timezone rules at the reference time, including negative seasonal adjustments
- at
- 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
- to
- With ?to= only: the other zone evaluated at the same instant
- unix
- Unix timestamp in seconds for the resolved instant. Always present; fractional seconds round down. Null for an ambiguous or unresolved source location
- to.at
- The converted local date and time, ISO with its UTC offset
- to.unix
- The same Unix timestamp as unix: both zones describe one instant
- targets
- 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
- location
- For explicit place inputs: input, status (resolved, ambiguous or not_found), candidates, truncated and source. Ambiguous/missing locations retain null clock fields. Choose a candidate timezone explicitly
Deep fields
- deep.name
- Friendly / generic name (e.g. Eastern Time)
- deep.offset_minutes
- UTC offset in whole minutes, truncated toward zero
- deep.offset_seconds
- Exact UTC offset in seconds, including historical subminute offsets
- deep.next_dst
- Next offset transition after the reference time, or null
- targets[].deep
- With deep=true: name, offset_minutes and offset_seconds for this destination
- deep.timezone_database_version
- The actual pinned IANA rules edition used for this answer; present in source deep only
- deep.resolution
- 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_offset
- Standard UTC offset at the requested instant, as ±HH:MM[:SS]. Null when unresolved
- deep.standard_offset_seconds
- Exact standard UTC offset in seconds, from the same timezone rules
- deep.dst_offset_seconds
- Actual offset minus standard offset, in seconds. Preserves zero, negative saving and double daylight saving
- deep.season
- 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
- Find an open store nearby
- Show an event in the visitor's time zone
- Find shared working hours
- Show opening hours on a business page
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?
Yes. A lookup or conversion to up to ten destinations uses one pooled request on every plan, including optional detail. 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.
Time, included.
One request. Up to ten destinations. Every plan.
Start includes 1M API requests a month for $20/mo.
Ready for busy moments.Start includes 6,000 requests per minute, with extra capacity for bursts. Rate limits