Overview
Timezone Lookup works by retrieving timezone data from a curated database and providing it in a structured format. The timezone database is updated regularly to ensure accurate and up-to-date information.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/timezonelookup?city=Harare" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/timezonelookup?city=Harare', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/timezonelookup?city=Harare",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/timezonelookup?city=Harare", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
cityRequired | string | The city name for which you want to get the data (e.g., Harare) |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"timezone": "Africa/Harare",
"timezone_offset": 120,
"date": "2025-12-17",
"time": "00:30",
"time24": "00:30:23",
"time12": "12:30:23 AM",
"day": "Wednesday",
"month": "December",
"year": "2025",
"unix": "1765924223",
"dst": false,
"dst_start": "2025-12-17 00:30:23",
"dst_end": "2025-12-17 00:30:23",
"dst_name": "CAT"
}
}Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
timezone | string | "Africa/Harare" | IANA timezone identifier for the city |
timezone_offset | number | 120 | Timezone UTC offset in minutes from GMT |
date | string | "2025-12-17" | Current date in YYYY-MM-DD format |
time | string | "00:30" | Current time in HH:MM format |
time24 | string | "00:30:23" | Current time in 24-hour HH:MM:SS format |
time12 | string | "12:30:23 AM" | Current time in 12-hour AM/PM format |
dayPremium | string | "Wednesday" | Current day of week name |
monthPremium | string | "December" | Current month name |
yearPremium | string | "2025" | Current year as string value |
unixPremium | string | "1765924223" | Current Unix timestamp in seconds |
dstPremium | boolean | false | Whether daylight saving time is currently active |
dst_startPremium | string | "2025-12-17 00:30:23" | DST start date and time in full format |
dst_endPremium | string | "2025-12-17 00:30:23" | DST end date and time in full format |
dst_namePremium | string | "CAT" | Daylight saving time zone abbreviation |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- World Clock
- Use the Timezone Lookup API to get timezone data for a world clock. Use the data to display time zones, track time differences, and manage global operations
- Travel Planning
- Plan travel by using the Timezone Lookup API to get timezone data for destinations. Use the data to schedule flights, book accommodations, and manage itinerary
- Meeting Scheduler
- Schedule meetings by using the Timezone Lookup API to get timezone data for participants. Use the data to coordinate time zones, set meeting times, and avoid scheduling conflicts
- Time Conversion
- Convert time by using the Timezone Lookup API to get timezone data for time zones. Use the data to calculate time differences, synchronize clocks, and manage time zones
Other ways to use Timezone Lookup
Set up Timezone Lookup on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
Pages that use this API:
- GraphQLPlatform
More in Data Lookup: