World Time API
World Time is a simple tool for getting the current time in any city. It returns the current time, date, and more.
The World Time API provides reliable and fast access to world time data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.
To use World Time, 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/worldtimeCode Examples
Here are examples of how to call the World Time API in different programming languages:
curl -X GET \
"https://api.apiverve.com/v1/worldtime" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/worldtime', {
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/worldtime', headers=headers)
data = response.json()
print(data)const https = require('https');
const url = require('url');
const options = {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
};
const req = https.request('https://api.apiverve.com/v1/worldtime', options, (res) => {
let data = '';
res.on('data', (chunk) => data += chunk);
res.on('end', () => console.log(JSON.parse(data)));
});
req.end();<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/worldtime');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'GET');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
'X-API-Key: your_api_key_here',
'Content-Type: application/json'
]);
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);
?>package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/worldtime", 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))
}require 'net/http'
require 'json'
uri = URI('https://api.apiverve.com/v1/worldtime')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'
response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;
class Program
{
static async Task Main(string[] args)
{
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");
var response = await client.GetAsync("https://api.apiverve.com/v1/worldtime");
response.EnsureSuccessStatusCode();
var responseBody = await response.Content.ReadAsStringAsync();
Console.WriteLine(responseBody);
}
}Authentication
The World Time 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 World Time API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the World Time API:
Get City Time
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
city | string | required | The city name for which you want to get the current time (e.g., New York) | - |
Response
The World Time API returns responses in JSON, XML, YAML, and CSV formats:
Example Responses
{
"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"
}
]
}
}<?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>
<search>San Francisco</search>
<foundCities>
<foundCitie>
<city>San Francisco</city>
<city_ascii>San Francisco</city_ascii>
<country>Argentina</country>
<iso2>AR</iso2>
<iso3>ARG</iso3>
<province>Córdoba</province>
<timezone>America/Argentina/Cordoba</timezone>
<time>19:33</time>
<time24>19:33:04</time24>
<time12>07:33:04 PM</time12>
<date>2025-12-16</date>
<day>Tuesday</day>
<month>December</month>
<year>2025</year>
<unix>1765924384</unix>
<dst>false</dst>
<dst_start>2025-12-16 19:33:04</dst_start>
<dst_end>2025-12-16 19:33:04</dst_end>
<dst_name>-03</dst_name>
</foundCitie>
<foundCitie>
<city>San Francisco</city>
<city_ascii>San Francisco</city_ascii>
<country>United States of America</country>
<iso2>US</iso2>
<iso3>USA</iso3>
<province>California</province>
<state_ansi>CA</state_ansi>
<timezone>America/Los_Angeles</timezone>
<time>14:33</time>
<time24>14:33:04</time24>
<time12>02:33:04 PM</time12>
<date>2025-12-16</date>
<day>Tuesday</day>
<month>December</month>
<year>2025</year>
<unix>1765924384</unix>
<dst>false</dst>
<dst_start>2025-12-16 14:33:04</dst_start>
<dst_end>2025-12-16 14:33:04</dst_end>
<dst_name>PST</dst_name>
</foundCitie>
</foundCities>
</data>
</response>
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
| key | value |
|---|---|
| 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 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 |
|---|---|---|
search | string | |
| [ ] Array items: | array[2] | |
â”” city | string | |
â”” city_ascii | string | |
â”” country | string | |
â”” iso2 | string | |
â”” iso3 | string | |
â”” province | string | |
â”” timezone | string | |
â”” time | string | |
â”” time24 | string | |
â”” time12 | string | |
â”” date | string | |
â”” day | string | |
â”” month | string | |
â”” year | string | |
â”” unix | string | |
â”” dst | boolean | |
â”” dst_start | string | |
â”” dst_end | string |
Headers
Required and optional headers for World Time API requests:
| Header Name | Required | Example Value | Description |
|---|---|---|---|
X-API-Key | required | your_api_key_here | Your APIVerve API key. Found in your dashboard under API Keys. |
Accept | optional | application/json | Specify response format: application/json (default), application/xml, or application/yaml |
User-Agent | optional | MyApp/1.0 | Identifies your application for analytics and debugging purposes |
X-Request-ID | optional | req_123456789 | Custom request identifier for tracking and debugging requests |
Cache-Control | optional | no-cache | Control caching behavior for the request and response |
GraphQL AccessALPHA
Access World Time through GraphQL to combine it with other API calls in a single request. Query only the world time 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 {
worldtime(
input: {
city: "San Francisco"
}
) {
search
foundCities
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The World Time API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call World Time directly from browser-based applications without proxy servers.
| CORS Header | Value | Description |
|---|---|---|
Access-Control-Allow-Origin | * | Accepts requests from any origin |
Access-Control-Allow-Methods | * | Accepts any HTTP method |
Access-Control-Allow-Headers | * | Accepts any request headers |
Browser Usage: You can call World Time directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.
Rate Limiting
World Time API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all World Time users.
| Plan | Rate Limit | Description |
|---|---|---|
| Free | 5 requests/min | Hard rate limit enforced - exceeding will return 429 errors |
| Starter | No Limit | Production ready - standard traffic priority |
| Pro | No Limit | Production ready - preferred traffic priority |
| Mega | No Limit | Production ready - highest traffic priority |
Learn more about rate limiting →
Rate Limit Headers
When rate limits apply, each World Time response includes headers to help you track your usage:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests allowed per time window |
X-RateLimit-Remaining | Number of requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the rate limit window resets |
Handling Rate Limits
Free Plan: When you exceed your rate limit, World Time returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.
Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.
Best Practices for World Time:
- Monitor the rate limit headers to track your World Time usage (Free plan only)
- Cache world time responses where appropriate to reduce API calls
- Upgrade to Pro or Mega for guaranteed no-throttle World Time performance
Note: World Time rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using World Time on Free tier.
Error Codes
The World Time API uses standard HTTP status codes to indicate success or failure:
| Code | Message | Description | Solution |
|---|---|---|---|
200 | OK | Request successful, data returned | No action needed - request was successful |
400 | Bad Request | Invalid request parameters or malformed request | Check required parameters and ensure values match expected formats |
401 | Unauthorized | Missing or invalid API key | Include x-api-key header with valid API key from dashboard |
403 | Forbidden | API key lacks permission or insufficient credits | Check credit balance in dashboard or upgrade plan |
429 | Too Many Requests | Rate limit exceeded (Free: 5 req/min) | Implement request throttling or upgrade to paid plan |
500 | Internal Server Error | Server error occurred | Retry request after a few seconds, contact support if persists |
503 | Service Unavailable | API temporarily unavailable | Wait and retry, check status page for maintenance updates |
Learn more about error handling →
Need help? Contact support with your X-Request-ID for assistance.
Integrate World Time with SDKs
Get started quickly with official World Time SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.
Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.
Integrate World Time with No-Code API Tools
Connect the World Time API to your favorite automation platform without writing code. Build workflows that leverage world time data across thousands of apps.





All platforms use your same API key to access World Time. Visit our integrations hub for step-by-step setup guides.
Frequently Asked Questions
How do I get an API key for World Time?
How many credits does World Time cost?
Each successful World Time 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 world time lookups.
Can I use World Time in production?
The free plan is for testing and development only. For production use of World Time, 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 World Time from a browser?
What happens if I exceed my World Time credit limit?
When you reach your monthly credit limit, World Time 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.



