Questions about the Timezone Lookup API

The things developers ask before wiring up the Timezone Lookup 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
What timezone format should I use?
Use IANA timezone identifiers like "America/New_York", "Europe/London", or "Asia/Tokyo". These are the standard format used by most programming languages.
Does it handle daylight saving time?
Yes, the API automatically accounts for DST. The dst field indicates if DST is currently active, and dst_start/dst_end show transition dates.
Can I get time for multiple timezones at once?
Each request returns data for one timezone. Make parallel requests to get multiple timezones efficiently.
What is the timezone_offset field?
The UTC offset in minutes. For example, -300 means UTC-5 (5 hours behind UTC). This changes when DST is active.
How accurate is the time?
Our servers are synchronized with NTP time sources. The returned time is accurate to within a second, though network latency adds minor delay.
Can I convert between timezones?
Get the current time for both timezones and use the unix timestamp for accurate conversion. The unix field is timezone-independent.

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

Scaling up?

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

Contact sales