Resolve timezone information for a target
Use timezone resolution when the main question is zone identity and metadata rather than the formatted current time.
Open endpointGuide
Timezone Lookup API by IANA zone, IP, coordinates, or offset
The strongest timezone APIs make input strategy and ambiguity handling clear before you ship.
Different inputs imply different certainty
An IANA zone is usually authoritative. An IP address is probabilistic and user-context dependent. Coordinates are geographic and often highly accurate. A raw offset is the weakest representation because multiple zones can share it.
The docs should explain that hierarchy so buyers can tell whether the API fits their product model before they hit the pricing page.
Offset matching is useful but not identical to zone identity
When you only know a UTC offset, the result can include multiple matching zones rather than a single canonical answer. That distinction matters for scheduling, DST handling, and anything user-facing.
Related endpoints
Get the current time for a target
Use this route to validate selector resolution and inspect the canonical single-target time payload.
Open endpointDaylight-saving status for a target
Use DST status when offset change awareness matters to scheduling, billing windows, or user-facing time displays.
Open endpoint