Quickstart
Get a single request working with RapidAPI headers, a base URL, and one successful response example.
Open quickstartDocumentation
A clean docs surface with the full public API behind it.
Start with the operational rules, then move into endpoint-level detail, raw Swagger, and SEO-targeted guides for the most common time and timezone workflows.
Concepts
Understand selector families, bulk mode limits, signed responses, and the embeddable clock model before you branch into routes.
Open conceptsEndpoints
Every public operation gets natural-language explanation, parameter notes, code tabs, and expandable deep detail.
Open endpointsConcepts
Selector families and target resolution
Choose one target strategy per request and keep that rule consistent across your integration.
Read conceptBulk mode, partial failures, and error handling
Bulk mode is intentionally narrow, and per-item failures should be treated differently from request-level errors.
Read conceptSigned JSON responses and verification
Signing is optional, explicit, and documented as a verification workflow rather than a generic response flag.
Read conceptEmbeddable clock output and style selection
The clock route is an output feature, not a JSON helper, and the docs should reflect that difference clearly.
Read conceptEndpoints
Public signing key set
Use this route when a downstream service needs to verify signed JSON responses from the public API.
Open endpointGet the current time for a target
Use this route to validate selector resolution and inspect the canonical single-target time payload.
Open endpointConvert a timestamp into a target timezone or offset
Use conversion when you already know the source instant and need the target rendered in another timezone or offset.
Open endpointDifference between two instants
Use diff when you need the distance between two explicit instants rather than a relative now-to-target calculation.
Open endpointAdd modifiers to a timestamp
Use add when you want the API to shift a timestamp by explicit modifiers and then resolve the result in a target context.
Open endpointCalendar projection for a target instant
Use calendar projection when you want structured calendar fields for a target instant rather than only a formatted timestamp.
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 endpointRender a live HTML clock
Use the clock route when you want embeddable HTML output instead of building and styling a live clock component yourself.
Open endpointTime elapsed since or remaining until a reference instant
Use elapsed when you need time since or time until a reference instant, optionally relative to another explicit comparison instant.
Open endpointResolve timezone information for a target
Use timezone resolution when the main question is zone identity and metadata rather than the formatted current time.
Open endpointGuides
World Time API for production apps
How to evaluate a world time API when you need more than a bare UTC conversion utility.
Read GuideTimezone Lookup API by IANA zone, IP, coordinates, or offset
The strongest timezone APIs make input strategy and ambiguity handling clear before you ship.
Read GuideUTC, Unix, and wall-clock timestamp conversion API
Conversion is where timestamp inputs, source timezone context, and formatting choices start to matter.
Read GuideDST and business-day calculations API
Daylight-saving changes and business-day logic are where time APIs stop being trivial utilities.
Read Guide