Convert 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 endpointGuide
UTC, Unix, and wall-clock timestamp conversion API
Conversion is where timestamp inputs, source timezone context, and formatting choices start to matter.
Timestamp conversion is not only format translation
Real conversion workflows need to preserve intent when a caller submits Unix seconds, Unix milliseconds, or an ISO wall-clock time. The docs should help developers see when they are converting an instant versus interpreting a local time.
That is why the source timezone fields matter on routes that accept ISO values without explicit offsets.
Formatting is a delivery concern, not the source of truth
Custom format output is useful for display, but canonical fields like UTC and Unix values should remain the source of truth in downstream code. The endpoint pages repeat that principle so developers do not accidentally parse a human field as structured data.
Related endpoints
Add 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 endpoint