How do I authenticate?

Create a token on your API tokens page and send it in the Authorization header as a bearer token. Every token on your account shares its plan, and a token works once your email is verified.

Where does the data come from?

Offsets and daylight saving rules come from the tz database, the public source that operating systems and programming languages use. Every response names the release it was computed with in meta.tzdb_version (2026d today).

Will changes to the API break my integration?

The API is versioned under /v1. We add endpoints, fields and parameters without notice, and give at least 90 days' notice by email and in the docs before removing or changing anything in a way that could break an existing integration, or retiring a version, except when a change is urgently needed for security or legal reasons.

Is there a version without a key?

Yes. worldtime.timezone.io is a free, keyless replacement for the retired WorldTimeAPI, with the same paths and fields. The full API needs a free key.

Developer API

Free Time Zone API

Live UTC offsets, daylight saving changes, abbreviations, conversions, cities and coordinates, as clean JSON computed for the moment you ask. 100,000 requests a month free, no card needed.

Get a free key Read the quickstart

Plans · How it compares · FAQ

GET /v1/timezones/America/New_YorkLive

{
  "data": {
    "iana": "America/New_York",
    "display_name": "New_York",
    "observes_dst": true,
    "is_mainland": true,
    "coordinates": {
      "latitude": 40.71416,
      "longitude": -74.00638
    },
    "country": {
      "code": "US",
      "name": "United States"
    },
    "current": {
      "datetime": "2026-09-28T01:08:19-04:00",
      "utc_datetime": "2026-09-28T05:08:19Z",
      "utc_offset": "-04:00",
      "utc_offset_seconds": -14400,
      "abbreviation": "EDT",
      "name": "Eastern Daylight Time",
      "is_dst": true
    },
    "standard": {
      "utc_offset": "-05:00",
      "utc_offset_seconds": -18000,
      "abbreviation": "EST",
      "name": "Eastern Standard Time"
    },
    "dst": {
      "savings_seconds": 3600,
      "next_transition": {
        "type": "fall_back",
        "at": "2026-11-01T06:00:00Z",
        "utc_offset_after": "-05:00",
        "abbreviation_after": "EST",
        "clock_change_seconds": -3600
      }
    },
    "links": {
      "self": "https://api.timezone.io/v1/timezones/America/New_York",
      "country": "https://api.timezone.io/v1/countries/US",
      "abbreviation": "https://api.timezone.io/v1/abbreviations/eastern-daylight-time",
      "web": "https://www.timezone.io/iana/America/New_York"
    }
  },
  "meta": {
    "tzdb_version": "2026d",
    "generated_at": "2026-09-28T05:08:19+00:00"
  }
}

What's there

10 endpoints, one token.

What's different

Built for the hard parts of time.

The names people use

Every zone comes with its friendly name and abbreviation, like Eastern Daylight Time and EDT. Ask for “CST” and you get every standard that uses it, not a guess.

Daylight saving, disclosed

Convert a time the clocks skip in spring, or pass twice in autumn, and the response says so, which moment it picked, and how to ask for the other.

Computed when you ask

Current offsets, daylight saving state and the next clock change are worked out for the moment of your request, so they are right on the day the clocks change.

The tz release on every answer

Each response names the time zone database release behind it (2026d today) in meta.tzdb_version, so you can see when a rule change reached you.

Your first request

Any language that speaks HTTPS.

Send your key as a bearer token and read JSON back. There's no SDK to install, and every response has the same shape: the payload under data, the tz release under meta.

Browse the docs →

curl https://api.timezone.io/v1/timezones/America/New_York \
  -H "Authorization: Bearer YOUR_API_TOKEN"

Plans

Priced by volume.

See pricing →

Free$0 / month · 100,000 requests
Developer$20 / month · 1 million requests (coming soon)
Business$100 / month · 10 million requests (coming soon)

Prices in US dollars, plus applicable taxes.

How it compares

The honest version.

Other time zone APIs, as of September 2026. Some are cheaper or do things we don't, and the last column says so.

API	Free tier	Paid from	1 million requests a month	Uptime SLA	Where it's stronger
timezone.io	100,000 requests a month at 5 a second; commercial use allowed	$20 a month for 1 million requests at 25 a second (coming soon)	$20 a month (coming soon)	99.9% on Business (coming soon)	Friendly names, abbreviations, daylight-saving-aware conversion, cities with sun times and coordinates lookup, in one API.
Google Time Zone API	10,000 requests a month; needs a billing account	$5 per 1,000 requests, less at higher volumes	About $3,550 a month	99.9% (Maps Platform SLA)	Google's scale: up to 30,000 requests a minute. One call only: coordinates and a timestamp to a zone.
TimeZoneDB	Unlimited at 1 request a second, for personal and non-commercial use	$5 a month or $50 a year, no rate limit	$5 a month	None published	Far cheaper at high volume. Premium adds lookups by city name and IP address.
timeapi.io	Free for everyone, no key; limits not published	None yet	$0	None; its FAQ says one may come with paid plans	No sign-up at all. Current time by coordinates or IP address.
AbstractAPI	5,000 requests at 1 a second	$19 a month for 50,000 requests at 3 a second	$99 a month, at 50 requests a second	99.99% on Enterprise (custom pricing)	Lookups by place name or IP address, and a higher per-second limit at a million requests.

Checked on each provider's own pages in September 2026: Google Time Zone API, TimeZoneDB, timeapi.io, AbstractAPI. Google's figure adds up its volume tiers after the free 10,000. AbstractAPI's are the monthly figures from the price slider on its page, which shows other numbers before the slider loads. Prices change: tell us if one here is out of date.

Frequently asked questions

Keys, versions and the data behind the API. Can't find what you need? Email [email protected].

How do I authenticate?: Create a token on your API tokens page and send it in the Authorization header as a bearer token. Every token on your account shares its plan, and a token works once your email is verified.
Where does the data come from?: Offsets and daylight saving rules come from the tz database, the public source that operating systems and programming languages use. Every response names the release it was computed with in meta.tzdb_version (2026d today).
Will changes to the API break my integration?: The API is versioned under /v1. We add endpoints, fields and parameters without notice, and give at least 90 days' notice by email and in the docs before removing or changing anything in a way that could break an existing integration, or retiring a version, except when a change is urgently needed for security or legal reasons.
Is there a version without a key?: Yes. worldtime.timezone.io is a free, keyless replacement for the retired WorldTimeAPI, with the same paths and fields. The full API needs a free key.

Questions about plans, quotas or billing are answered on the pricing page.

Need more, or an SLA?

Higher volumes, custom terms or a question about your integration: tell us what you're building.

Contact us