Local clocks · Timezone conversion
Time API
One event.
Everyone’s local time.
Get the local time for a timezone or place. Convert a meeting for your team, keep the right date in every destination, and handle daylight-saving changes explicitly.
Local time and conversions on every plan. Clock detail included automatically on paid plans.
Try it
New York
America/New_YorkUTC-04:00
Oct 26, 2026
Highlighted fields: Included on paid plans.
Use this request in your app
A time your application can use
See the request.
Keep the whole answer.
Choose a task to see its complete request and JSON. Read the timestamp with its timezone and UTC offset, so the instant stays clear.
A local clock with its timezone.
Read the local timestamp, UTC offset and daylight-saving status together. This is a recorded example; run the demo above for the current time.
Request
curl "https://api.parseapi.com/time?at=2026-08-29T19:00:00Z" \
-H "X-API-Key: YOUR_API_KEY" \
-H "X-API-Version: 2.1.0"Example response
Highlighted fields: Included on paid plans.
Meetings · Bookings · Notifications
One instant.
The right date everywhere.
A meeting at 3pm in New York can be tomorrow in Tokyo. Convert the source time into up to ten destinations in one request. Every result refers to the same Unix timestamp.
Build an event timezone displayNew York
America/New_YorkUTC-04:00
Aug 29, 2026
London
Europe/LondonUTC+01:00
Aug 29, 2026
Tokyo
Asia/TokyoUTC+09:00
Aug 30, 2026
Cities · Coordinates · Airport codes
Start with
the place you have.
Use a map pin, a city from a booking or an airport code from an itinerary. Time resolves the location to a timezone and returns its local clock.
IATA and ICAO lookups use recorded airport locations. Port codes and matched US street addresses are also supported. A place with several answers returns choices; an unknown place stays unresolved.
Explore location inputsJFK
John F. Kennedy International Airport
New York
America/New_YorkUTC-04:00
Sep 24, 2026
Daylight-saving changes
When 1:30
happens twice.
Ask for clarification when a local time repeats or is skipped. If your app has a policy, choose the earlier or later instant explicitly.
Use disambiguation=reject to ask. The API’s compatible default picks the earlier repeated time and moves a skipped time forward. An explicit UTC offset identifies the instant directly.
Resolve repeated and skipped timesFirst occurrence
UTC-04:00
05:30 UTC
Second occurrence
UTC-05:00
06:30 UTC
City · Postal · Point → Time
Use the timezone
you already have.
These location APIs already return a timezone identifier. Pass it straight to Time when you need a local clock or conversion; reuse the location answer you have.
- City → Time
Miami returns America/New_York.
/time/America/New_York
- Postal → Time
ZIP 10001 returns America/New_York.
/time/America/New_York
- Point → Time
39.77, -104.9 returns America/Denver.
/time/America/Denver
Timezone rules and location coverage
Keep the clock
with its context.
Use named timezone identifiers for local clocks and event conversion. Country and abbreviation searches can return several valid choices. Keep the chosen identifier with your event.
- Timezones and coordinates
- Timezone rules cover named zones. Coordinate lookup covers land and ocean; open-ocean coordinates use a nautical timezone.
- Place records
- City, airport and port lookups depend on recorded locations. Address matching is limited to supported US points. IP location is an estimate.
- Included on paid plans
- Paid plans automatically include readable timezone names, numeric offsets, seasonal clock changes and available local-time resolution. Ordinary local time and conversion stay complete on every plan.
From the example to your application
Your schedule.
Your way to build.
Call Time over HTTP, use an SDK in your language, or connect through MCP. Keep your secret key on your server.
Before you build.
What does the ordinary response include?
The timezone identifier, local timestamp, Unix seconds, UTC offset, abbreviation and daylight-saving status. Coordinates and location choices are included when they are needed to describe the input. Lookups and conversions use the shared API request allowance.
Can I convert one event for several destinations?
Yes. Send one source timezone and instant with up to ten target timezones. Every destination refers to the same Unix timestamp. If the input has no UTC offset, its date and time are interpreted in the source timezone.
What if the clocks change at that time?
A local time can occur twice or be skipped. Set disambiguation=reject when your app should ask. Choose earlier or later when you have a policy. The API default is compatible: the earlier occurrence for repeated times and a forward shift for skipped times.
Can I start with a city or an airport?
Yes. Time accepts city and country inputs, IATA or ICAO airport codes, recorded port codes, explicit IP addresses and matched US street addresses. Airport and port codes use recorded locations. These are location lookups, not flight or shipping schedules.
What happens when a place has more than one timezone?
The response returns location candidates so your application can ask which place the person means. A country can also have several timezone choices. An unknown location stays unresolved; IP location is an estimate.
What do paid plans include?
Paid plans automatically include a readable timezone name, numeric offsets, seasonal clock changes and available local-time resolution information in the same response. The ordinary timestamp and conversion results keep their meaning. Basic local time and conversion are included on every plan.
Can I use a timezone I already have?
Yes. City, Postal and Point return timezone identifiers that Time accepts directly. Reuse the identifier when you need a clock or conversion response; the original location does not need to be looked up again.
How current are the timezone rules?
Time calculations use the maintained timezone-rule catalog. Airport, port, address, city and IP records have their own coverage and observation dates. A current rule catalog does not establish that every location record has been refreshed.
Time API pricing
Put Time in your app.
Time lookups and conversions use your API request allowance, shared across ParseAPI products.
Free
See the current allowance on Plans.
Local time and conversions.
Room to grow
See the current allowance on Plans.
Includes timezone and clock-change detail automatically.