Introducing the TimeZoneMeet API
Time-zone math is a classic source of bugs: ambiguous abbreviations, stale offsets, and daylight-saving transitions that silently move a meeting an hour. We built TimeZoneMeet to get this right, and now you can use the same engine in your own product — for free.
Two ways to use it
- The embed widget — show live world clocks with two lines of HTML. No key, no build step, no code.
- The JSON API — get raw conversion data for your own UI or backend, with a free API key (1,000 requests/day).
1. The no-code widget
Paste this into any page — a dashboard, wiki, or status page — and it renders live, ticking clocks:
<div data-tzm-clock data-zones="America/New_York,Europe/London,Asia/Tokyo"></div> <script src="https://timezonemeet.app/embed.js" async></script>
It inherits your fonts, supports light/dark, and updates every minute. Full options are in the widget docs.
2. The JSON API
Want the data to build your own interface? Grab a free API key and call the endpoint:
curl 'https://timezonemeet.app/api/convert?utc=now&tz=Europe/Paris,Asia/Tokyo' \ -H 'X-API-Key: tzm_live_xxxxx'
You get the local wall-clock time, a zoned ISO-8601 string, the UTC offset, the day of week, and a DST flag for each zone — DST and half-hour zones handled correctly. There's a machine-readable OpenAPI spec too, so you can import it into Postman or generate a typed client.
Why a key? It keeps usage accountable and lets us be generous to good actors while stopping abuse — the standard freemium model. The free tier (1,000 requests/day) covers virtually every dashboard and integration.
What it's good for
- World-clock panels on internal dashboards and team wikis.
- Showing a customer's local time in support tools and CRMs.
- Server-side scheduling logic that needs correct offsets over time.
- Anywhere you'd otherwise hand-roll fragile
+N hoursmath.
Get started
Get a free API key → Read the docs
Free for any use with attribution — keep the "Times by TimeZoneMeet" link where you display the data (the widget does this for you). See the Terms.