How do I get the current time?

GET /time returns UTC now. Add an IANA timezone, such as /time/America/New_York, or pass lat and lon to get local time at a coordinate. Every answer includes at, the ISO datetime with its offset, and unix, the timestamp in whole seconds.

Can I convert between timezones?

Yes. Add to= with the destination zone. /time/America/New_York?to=Asia/Tokyo&at=2026-08-29T15:00 returns 2026-08-30T04:00:00+09:00 in to.at. Both zones describe the same instant and return the same Unix timestamp.

How do daylight-saving changes work?

offset and dst follow timezone rules at the requested instant, including negative DST adjustments. Optional deep.next_dst gives the next source-zone offset change, or null when none is found in the next 400 days. With to, repeated local time selects the earlier occurrence and skipped time moves forward by the clock gap. An explicit offset identifies the exact occurrence.

Can I check a past or future time?

Pass at= with an ISO timestamp. An explicit Z or UTC offset identifies one instant. With to=, an offsetless timestamp means local time in the source zone; without to=, it means UTC. Invalid dates return 400.

What about half-hour offsets and the ocean?

Fractional-hour offsets are included, such as India at UTC+05:30 and Nepal at UTC+05:45. Open ocean returns a nautical Etc/GMT zone. These ids have reversed signs: Etc/GMT+3 means UTC-03:00. The offset and local datetime fields use the normal sign.

Is Time included on Free?

Yes. Current time, timezone lookup, conversion, and optional deep detail each use one pooled request on every plan. Add deep=true for friendly zone name, numeric offsets, and the next source-zone clock change. The conversion target includes its own friendly name and numeric offsets.

Does /timezone still work?

Yes. Existing /timezone integrations continue to work. /time is the name to use for new integrations.

GET /time/{timezone}

Time API

One instant. Every local time.

The local time, right now. Choose a timezone.

Example response/time/America%2FNew_York?at=2026-08-29T19:00:00Z

{
  "timezone": "America/New_York",
  "abbreviation": "EDT",
  "offset": "-04:00",
  "dst": true,
  "at": "2026-08-29T15:00:00-04:00",
  "unix": 1788030000,
  ?deep=true
}

What comes back.

Local date and time as ISO 8601 with the resolved UTC offset. Always present; now unless ?at= selects a moment. Null for an unresolved coordinate

unix

Unix timestamp in seconds for the resolved instant. Always present; fractional seconds round down. Null for an unresolved coordinate

timezone

IANA timezone id. Nautical Etc/GMT zone over open ocean

deep.name

Friendly / generic name (e.g. Eastern Time)

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

deep.offset_minutes

UTC offset in whole minutes, truncated toward zero

deep.offset_seconds

Exact UTC offset in seconds, including historical subminute offsets

dst

Daylight-saving indicator from the timezone rules at the reference time, including negative seasonal adjustments

deep.next_dst

Next offset transition after the reference time, or null

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

Get the time

Pass an IANA zone or coordinates. Get local time with its UTC offset and Unix timestamp.

Convert it

Add to= for another zone. Both local dates and times describe the same instant, even across midnight.

Plan ahead

Pass at= for a specific moment. Add deep=true for the next clock change, included on every plan.

Coverage

Every IANA timezone. Land and ocean.

ISO + Unix
every answer: Every plan
included

Get the local time in New York, Tokyo, or at a coordinate. Every answer includes an ISO datetime with its UTC offset, a Unix timestamp, the IANA timezone, and DST status. Add deep=true for the friendly name, numeric offsets, and next source-zone clock change, included on every plan. Bare /time gives you UTC.

Add ?at= to check a specific moment. Add ?to= to show that same instant in another zone. Both sides carry their own local date, time, and offset, with the same Unix timestamp. Meetings cross midnight. Clocks change. Your timestamps stay unambiguous.

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.

54ms

86ms

APAC

70ms

LatAm

78ms

169ms

See live status →

Time, included.

Current time, timezone lookup, and conversion. Every plan.

Start includes 1M API requests a month for $20/mo.

Get started Compare plans Read the docs

Make your first request.

One key works across the APIs. Copy a request in your language and get JSON back.

curl "https://api.parseapi.com/time/America%2FNew_York?at=2026-08-29T19:00:00Z" \
  -H "X-API-Key: YOUR_API_KEY"

// Example response · 200
{
  "timezone": "America/New_York",
  "abbreviation": "EDT",
  "offset": "-04:00",
  "dst": true,
  "at": "2026-08-29T15:00:00-04:00",
  "unix": 1788030000
}

?deep=true Friendly zone name, numeric offset representations and the next offset transition. Included on every plan, with no additional charge.

API reference SDKs Keys and authentication

Every response field

Response fields

latitude: Input latitude (coords path only)
longitude: Input longitude (coords path only)
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 unresolved coordinate
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 unresolved coordinate
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

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

Build with Time

All tutorials →

QUESTIONS

How do I get the current time?: GET /time returns UTC now. Add an IANA timezone, such as /time/America/New_York, or pass lat and lon to get local time at a coordinate. Every answer includes at, the ISO datetime with its offset, and unix, the timestamp in whole seconds.
Can I convert between timezones?: Yes. Add to= with the destination zone. /time/America/New_York?to=Asia/Tokyo&at=2026-08-29T15:00 returns 2026-08-30T04:00:00+09:00 in to.at. Both zones describe the same instant and return the same Unix timestamp.
How do daylight-saving changes work?: offset and dst follow timezone rules at the requested instant, including negative DST adjustments. Optional deep.next_dst gives the next source-zone offset change, or null when none is found in the next 400 days. With to, repeated local time selects the earlier occurrence and skipped time moves forward by the clock gap. An explicit offset identifies the exact occurrence.
Can I check a past or future time?: Pass at= with an ISO timestamp. An explicit Z or UTC offset identifies one instant. With to=, an offsetless timestamp means local time in the source zone; without to=, it means UTC. Invalid dates return 400.
What about half-hour offsets and the ocean?: Fractional-hour offsets are included, such as India at UTC+05:30 and Nepal at UTC+05:45. Open ocean returns a nautical Etc/GMT zone. These ids have reversed signs: Etc/GMT+3 means UTC-03:00. The offset and local datetime fields use the normal sign.
Is Time included on Free?: Yes. Current time, timezone lookup, conversion, and optional deep detail each use one pooled request on every plan. Add deep=true for friendly zone name, numeric offsets, and the next source-zone clock change. The conversion target includes its own friendly name and numeric offsets.
Does /timezone still work?: Yes. Existing /timezone integrations continue to work. /time is the name to use for new integrations.

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

Get started Compare plans Read the docs