Skip to main content
GET
Get the timezone for a specific city. The country and state codes in the path are not redundant — they’re enforced server-side as an ownership check: a city ID is only resolved if it actually belongs to the given state inside the given country. This prevents “city-ID spoofing” — a caller can’t learn the timezone of an arbitrary city by trying its ID under a different country/state pair.
Availability: All plans (Community and above). Only an API key is required.
Responses are cached server-side for 24 hours. The cache key includes country, state, and city ID, so the ownership check holds on cache HIT — a city ID looked up under one (ciso, siso) pair won’t satisfy a request under a different pair.

Authentication

string
required
Your API key for authentication

Path Parameters

string
required
Country code: ISO 3166-1 alpha-2 (US), alpha-3 (USA), or numeric CSC ID. Case-insensitive.
string
required
State/province code (e.g. CA for California). Case-insensitive.
integer
required
Numeric CSC city ID. Get this from /v1/countries/:ciso/states/:siso/cities or /v1/cities.

Response

Same shape as the country and state timezone endpoints:
string
Canonical IANA timezone name (e.g. "America/Los_Angeles").
string
Locale-aware short name at request time.
string
Standard UTC offset in ±HH:MM form.
string
DST UTC offset in ±HH:MM form.
boolean
Whether DST is in effect at request time.

Notes on city_id

The city_id is the same numeric ID returned by all list endpoints (/v1/countries/:ciso/states/:siso/cities, /v1/cities, etc.). If you stored a city ID in your own database, this endpoint is the canonical way to look up its timezone without re-fetching the full city record.