Date & Time Formatting API

Format an instant using safe named presets in any IANA timezone.

GET/api/v1/format

What It Does

Format an instant using safe named presets in any IANA timezone.

HTTP method: GET
Authentication: Public read-only; Bearer keys supported
Version: v1

Parameters

Name	Type	Required	Description
`timestamp`	integer	No	Unix seconds. Defaults to now. Example: `1788946200`
`timezone`	string	No	IANA timezone. Example: `Asia/Karachi`
`format`	string	No	iso, rfc3339, date, time or datetime. Example: `rfc3339`

Request Examples

cURL

curl -s 'https://worldclock.to/api/v1/format?timestamp=1788946200&timezone=Asia/Karachi&format=rfc3339'

JavaScript

const response = await fetch("https:\/\/worldclock.to\/api\/v1\/format?timestamp=1788946200&timezone=Asia\/Karachi&format=rfc3339");
const result = await response.json();
console.log(result.data);

PHP

$response = wp_remote_get('https://worldclock.to/api/v1/format?timestamp=1788946200&timezone=Asia/Karachi&format=rfc3339');
 = json_decode(wp_remote_retrieve_body(), true);

Python

import requests

response = requests.get("https:\/\/worldclock.to\/api\/v1\/format?timestamp=1788946200&timezone=Asia\/Karachi&format=rfc3339")
response.raise_for_status()
print(response.json()["data"])

Example Response

The values below illustrate the response shape. Live current-time fields are generated dynamically by the endpoint.

JSON

{
    "success": true,
    "data": {
        "formatted": "2026-09-09T14:30:00+05:00",
        "format": "rfc3339",
        "timezone": "Asia/Karachi",
        "unix": 1788946200
    },
    "meta": {
        "version": "v1",
        "timezone": "Asia/Karachi",
        "timestamp": 1788946200
    }
}

Response Properties

Every successful response contains success: true, endpoint-specific data, and a meta object. The table below documents the public fields for this endpoint.

Property	Meaning
`success`	Boolean indicating whether the request completed successfully.
`meta.version`	Published API response version.
`meta.timestamp`	Unix timestamp for the API response instant.
`meta.timezone`	Timezone context used by the response.
`meta.rate_limit`	Per-client fair-use limit and remaining-request information on public transports.
`data.formatted`	Formatted local date/time string.
`data.format`	Named safe format preset used by the endpoint.
`data.timezone`	IANA timezone used for output.
`data.unix`	Unix timestamp represented by the formatted value.

Errors use success: false with a stable machine-readable error code and a safe human-readable message.

Errors & HTTP Status Codes

400 — invalid or missing parameter.
401 — API key required or invalid when key-only access is enabled.
404 — unknown city, country or endpoint.
429 — configured rate limit reached.
503 — API disabled or maintenance mode.

Rate Limits & Caching

Current fair-use configuration is 60 requests per minute and 5000 requests per day. Cache stable directory/calculation responses where appropriate; treat current-time output as point-in-time data.