Timezone Lookup API
Overview
To use Timezone Lookup, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/timezonelookupExample
How to call the Timezone Lookup API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/timezonelookup?city=Harare" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/timezonelookup?city=Harare', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/timezonelookup?city=Harare', headers=headers)
data = response.json()
print(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")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"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"
}
}Authentication
The Timezone Lookup API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Timezone Lookup API directly in your browser with live requests and responses.
Parameters
The Timezone Lookup API supports multiple query options. Use one of the following:
Option 1: Lookup Timezone by City
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
city | string | required | The city name for which you want to get the data (e.g., Harare) | - |
Option 2: Lookup Timezone by Timezone
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
timezone | string | required | The timezone name for which you want to get the data (e.g., America/New_York) | - |
Response
The Timezone Lookup API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<timezone>Africa/Harare</timezone>
<timezone_offset>120</timezone_offset>
<date>2025-12-17</date>
<time>00:30</time>
<time24>00:30:23</time24>
<time12>12:30:23 AM</time12>
<day>Wednesday</day>
<month>December</month>
<year>2025</year>
<unix>1765924223</unix>
<dst>false</dst>
<dst_start>2025-12-17 00:30:23</dst_start>
<dst_end>2025-12-17 00:30:23</dst_end>
<dst_name>CAT</dst_name>
</data>
</response>
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
| key | value |
|---|---|
| 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 Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
timezone | string | - | |
timezone_offset | number | - | |
date | string | - | |
time | string | - | |
time24 | string | - | |
time12 | string | - | |
day | string | - | |
month | string | - | |
year | string | - | |
unix | string | - | |
dst | boolean | - | |
dst_start | string | - | |
dst_end | string | - | |
dst_name | string | - |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Timezone Lookup through GraphQL to combine it with other API calls in a single request. Query only the timezone lookup data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
timezonelookup(
input: {
city: "Harare"
}
) {
timezone
timezone_offset
date
time
time24
time12
day
month
year
unix
dst
dst_start
dst_end
dst_name
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Timezone Lookup API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Timezone Lookup requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Timezone Lookup API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Timezone Lookup
Official Timezone Lookup packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Timezone Lookup works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Timezone Lookup?
How many credits does Timezone Lookup cost?
Each successful Timezone Lookup API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful timezone lookup lookups.
Can I use Timezone Lookup in production?
The free plan is for testing and development only. For production use of Timezone Lookup, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Timezone Lookup from a browser?
What happens if I exceed my Timezone Lookup credit limit?
When you reach your monthly credit limit, Timezone Lookup API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








