How do I authenticate with this API?
Create an API key in your Datpaq dashboard and send it with each request as a bearer token in the Authorization header.
Current Time API
Live offsets
DST auto-detect
ISO 8601
Live local time.For any timezone, right now.
One GET returns the current datetime, GMT offset, DST status, and zone abbreviation for any IANA zone. Comma-separated location format works too — no SDK, no body.
600+ · IANA zonesDST · auto-handled~12ms · typical p50ISO 8601 · datetime output
Why Current Time API
The world clock, as JSON.
Live Local Time
Returns the current datetime in ISO 8601 with the resolved zone offset — accurate to the second.
Every IANA Zone
Backed by moment-timezone. Hit any of the 600+ IANA identifiers — Africa/Lagos, Pacific/Auckland, you name it.
DST-Aware
The is_dst flag and the timezone abbreviation switch automatically across DST boundaries (EST↔EDT, GMT↔BST).
Comma Format Friendly
Pass `America, Arizona` and the API normalizes it to `America/Arizona`. Forgiving inputs, strict outputs.
Fast
Typical p50 around 12ms. No external lookups — moment-timezone in-process, Redis-backed metrics.
Simple to Integrate
Single GET, single required query param (`target`). Works from a browser, curl, or any HTTP client.
/api/v1/current-time
Endpoints, at a glance.
One route does the work, plus standard ops endpoints. Every route is GET with query-string auth.
GET/current-time
Current local time
Returns the current datetime, GMT offset, DST status, and abbreviation for any IANA timezone or comma-format location.
GET/health
Service health
Status, version, and timestamp. Root / redirects here.
GET/metrics
Prometheus metrics
Request counters, conversion counters, and processing duration histograms.
| Parameter | Type | Required | Description |
|---|---|---|---|
| target | string | yes | IANA zone (e.g. "America/New_York") or comma format (e.g. "America, Arizona") — converted to slash format automatically. |
| api_key | string | yes | API key via query string. Alternatively pass as x-api-key header. |
Requests & responses.
Pass an IANA identifier or comma-separated location. Always GET, always JSON.
IANA identifier
Pass the canonical zone string for the most reliable results.
GET https://datpaq.com/api/v1/current-time?api_key=YOUR_API_KEY&target=America/New_York
Comma format & DST
Forgiving input normalization and an example DST-active response.
GET https://datpaq.com/api/v1/current-time?api_key=YOUR_API_KEY&target=America, Arizona
Health
https://datpaq.com/api/v1/current-time/health
Metrics
https://datpaq.com/api/v1/current-time/metrics
Error reference
Predictable errors, always structured.
Every error response includes a correlationId for request tracing and a clear error message.
400Missing Parameter
Required target parameter not provided. Include ?target= with an IANA zone or comma-format location.
400Invalid Timezone
Zone identifier not recognized by moment-timezone. Must match the IANA database.
401Unauthorized
API key missing or invalid. Pass api_key as a query param or x-api-key as a header.
500Processing Error
Internal timezone conversion failure. The correlationId in the response helps with debugging.
Example error response
{
"success": false,
"error": "Invalid timezone specified. Please provide a valid timezone from the IANA database.",
"meta": {
"correlationId": "ghi789-jkl012",
"timestamp": "2026-04-06T10:30:00.000Z"
}
}FAQ
API questions developers ask first.
Is there a free tier?
Yes. Datpaq APIs include a free tier for building, testing, and small production workloads before you move to a paid plan.
What format do requests and responses use?
Datpaq APIs use REST over HTTPS and return JSON by default. Endpoint docs show the supported methods, query parameters, request bodies, and response fields.
Where can I see limits and errors?
Each API documents rate limits, validation rules, and error responses in the landing page and API docs so integrations can retry and fail cleanly.
The world clock, as JSON.
One GET returns the current datetime, offset, and DST status for any IANA zone or comma-format location.