Know the local time, anywhere.
IANA timezone, UTC offset, current time, and DST status — for any city or coordinates, in a single API call.
Trusted by teams at
Lookup by city name or geographic coordinates.
Timezone resolves any point on Earth by latitude/longitude, or any of 150+ major cities by name. Every response includes the IANA identifier, UTC offset, current UTC time, and whether the location is currently observing daylight saving time.
{
"timezone": "Asia/Tokyo",
"offset": "+09:00",
"current_time": "2026-07-11T23:00:00Z",
"is_dst": false
}
One GET request. No body, no parsing.
Pass a city name or lat/lon as query parameters. Your API key in the header. No SDK, no setup, no request body. The response is JSON, with the timezone fields nested one level under data.
GET /v1/places/timezone?city=Tokyo
Host: requiems.xyz
requiems-api-key: YOUR_API_KEY
Built for location-aware apps.
Timezone fits anywhere local time matters — scheduling, notifications, and travel alike.
Show the correct local time in scheduling tools
Resolve a user's timezone from their city or coordinates and render meeting times, deadlines, and calendar events correctly across regions.
Send notifications at the right local hour
Avoid waking users at 3am. Compute the local time for each recipient before triggering push notifications or emails.
Display arrival and departure times correctly
Travel and logistics platforms need to show times in the traveler's local timezone at each leg of a trip, not just UTC.
Handle daylight saving time transitions
Avoid off-by-one-hour bugs around DST changeovers by checking is_dst directly instead of hardcoding offset tables.
Set a sensible default timezone at signup
Look up the timezone from the user's city or IP-derived coordinates to pre-fill their account settings correctly.
Route support tickets by local business hours
Combine customer location with timezone data to route tickets to on-shift support agents in the right region.
Use together with complementary APIs.
Timezone works even better when paired with other Requiems APIs.
Benefit: Resolve the IANA timezone name first, then query World Time directly by name for lightweight repeated lookups.
Outcome: Faster follow-up lookups once the timezone ID is known.
Benefit: Convert a free-form address to coordinates, then feed those coordinates into Timezone for a complete location-to-time pipeline.
Outcome: Turn any address into a current local time in two API calls.
Benefit: Look up city metadata — population, country, coordinates — alongside timezone information in the same request flow.
Outcome: Richer location context for scheduling and local-time UIs.
Frequently Asked Questions
Still have questions? Contact support
Automate this with Requiems.
One API key. Timezone, plus 50+ other APIs across places, validation, finance, and more.