World Time is a simple tool for getting the current time in any city. It returns the current time, date, and more.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// World Time response payload
}
}
About the World Time API
World Time works by using the timezone database to determine the current time in any city. Based on the current time, it returns the current time, date, and more for any given city in the world
What people use it for
- Time Conversion
- Convert time between different time zones by using the World Time API. Get the current time in any city and convert it to another time zone
- Time Synchronization
- Synchronize time across different devices and systems by using the World Time API. Get the current time in any city and use it to set the time on your devices
- Scheduling Software
- Integrate the World Time API into scheduling software to display the current time in different cities. Use the API to show the current time in various time zones
- Travel Planning
- Plan travel itineraries by using the World Time API to determine the current time in different cities. Use the API to schedule flights, meetings, and events across different time zones
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use World Time
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the World Time API do?
How do I authenticate World Time API requests?
How much does the World Time API cost?
How fast is the World Time API?
What response formats does the World Time API support?
What HTTP method does the World Time API use?
Request parameters — GET /v1/worldtime
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
cityRequired | string | San Francisco | The city name for which you want to get the current time (e.g., New York) |
curl "https://api.apiverve.com/v1/worldtime?city=San%20Francisco" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
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.
Response — GET /v1/worldtime
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"search": "San Francisco",
"foundCities": [
{
"city": "San Francisco",
"city_ascii": "San Francisco",
"country": "Argentina",
"iso2": "AR",
"iso3": "ARG",
"province": "Córdoba",
"timezone": "America/Argentina/Cordoba",
"time": "19:33",
"time24": "19:33:04",
"time12": "07:33:04 PM",
"date": "2025-12-16",
"day": "Tuesday",
"month": "December",
"year": "2025",
"unix": "1765924384",
"dst": false,
"dst_start": "2025-12-16 19:33:04",
"dst_end": "2025-12-16 19:33:04",
"dst_name": "-03"
},
{
"city": "San Francisco",
"city_ascii": "San Francisco",
"country": "United States of America",
"iso2": "US",
"iso3": "USA",
"province": "California",
"state_ansi": "CA",
"timezone": "America/Los_Angeles",
"time": "14:33",
"time24": "14:33:04",
"time12": "02:33:04 PM",
"date": "2025-12-16",
"day": "Tuesday",
"month": "December",
"year": "2025",
"unix": "1765924384",
"dst": false,
"dst_start": "2025-12-16 14:33:04",
"dst_end": "2025-12-16 14:33:04",
"dst_name": "PST"
}
]
}
}
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 |
|---|---|---|---|
search | string | "San Francisco" | The city name that was searched for |
foundCities | array[2] | Array of cities matching the search query | |
city | string | "San Francisco" | City name as found in database |
city_ascii | string | "San Francisco" | City name in ASCII format |
country | string | "Argentina" | Full country name for the city |
iso2 | string | "AR" | ISO 3166-1 alpha-2 country code |
iso3 | string | "ARG" | ISO 3166-1 alpha-3 country code |
province | string | "Córdoba" | Province or state name for the city |
timezone | string | "America/Argentina/Cordoba" | IANA timezone identifier for the city |
time | string | "19:33" | Current time in short format (HH:MM) |
time24 | string | "19:33:04" | Current time in 24-hour format (HH:MM:SS) |
time12 | string | "07:33:04 PM" | Current time in 12-hour format with AM/PM |
date | string | "2025-12-16" | Current date in ISO format (YYYY-MM-DD) |
dayPremium | string | "Tuesday" | Day of week name (e.g., Monday, Tuesday) |
monthPremium | string | "December" | Month name (e.g., January, February) |
yearPremium | string | "2025" | Current year as string |
unixPremium | string | "1765924384" | Unix timestamp (seconds since epoch) |
dstPremium | boolean | false | Whether daylight saving time is active |
dst_startPremium | string | "2025-12-16 19:33:04" | DST start date and time (YYYY-MM-DD HH:MM:SS) |
dst_endPremium | string | "2025-12-16 19:33:04" | DST end date and time (YYYY-MM-DD HH:MM:SS) |
dst_namePremium | string | "-03" | DST timezone abbreviation or offset |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | World Time calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/worldtime
No SDK to install — this is a plain HTTPS call to /v1/worldtime with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/worldtime" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/worldtime
Install the Node.js SDK, then call the World Time API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/worldtimeconst res = await fetch("https://api.apiverve.com/v1/worldtime", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/worldtime
Install the Python SDK, then call the World Time API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-worldtimeimport requests
res = requests.get(
"https://api.apiverve.com/v1/worldtime",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/worldtime
Install the C# / .NET SDK, then call the World Time API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.WorldTimeusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/worldtime");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/worldtime
No SDK to install — this is a plain HTTPS call to /v1/worldtime with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/worldtime", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/worldtime
No SDK to install — this is a plain HTTPS call to /v1/worldtime with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/worldtime");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/worldtime
No SDK to install — this is a plain HTTPS call to /v1/worldtime with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/worldtime")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive World Time form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — World Time API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the World Time API.
Data Lookup
- ASN Lookup
- Bible
- Country Calling Code
- Dictionary
- Dog Breeds
- Emoji Lookup
- Gender Detector
- Gravatar Lookup
- IP Demographics
- Lottery Numbers
- Nobel Prizes
- Open Source Licenses
- Thesaurus
- Timezone Lookup
- Unicode Character Lookup
- World Time
- ZIP Demographics
Related articles
All articles →
The Timezone Bug That Cost Us a ClientA scheduled email went out at 3 AM instead of 9 AM. The client wasn't happy. Here's what went wrong.Read
Build a Lead Enrichment Pipeline That Actually WorksTurn email addresses into full customer profiles. Location, company, social links—automatically. Here's how to build it.Read
Weather APIs: Build a Dashboard That's Actually UsefulCurrent conditions, forecasts, air quality, sunrise times—here's how to build a weather dashboard users will love.Read