Questions about the World Time API

The things developers ask before wiring up the World Time API — what it returns, what it covers, and where the limits are. Straight answers, no fluff.

Everything you asked

Still stuck on something specific? The team answers real integration questions directly.

Contact support
How do I query the API?
Simply provide a city name (e.g., "New York", "London", "Tokyo"). The API will find matching cities and return their current time, timezone, and date information.
How does the API handle Daylight Saving Time?
The API automatically accounts for DST. The response includes isDST (boolean) and the current offset. When DST transitions occur, the offset updates automatically based on the timezone's rules.
Can I convert between timezones?
Yes! Use the timezone conversion endpoint to convert any timestamp from one timezone to another. Perfect for scheduling meetings across global teams or calculating international delivery times.
How accurate is the time?
Our servers sync with NTP (Network Time Protocol) for accuracy within milliseconds. The returned time reflects the exact moment of the API call.
What metadata is included?
Beyond just the time, we return: UTC offset, DST status, day of week, week of year, Unix timestamp, and formatted date/time strings. Everything you need for display and calculations.
What if multiple cities have the same name?
The API returns an array of foundCities, so you may receive multiple matches. Each result includes the country and province to help distinguish between cities with the same name.

Answer the last question by building. Free tier, no card — run the World Time API in minutes.

Scaling up?

Volume pricing, custom SLAs, and dedicated support for high-traffic teams.

Contact sales