World Time API

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

Beta

GraphQL

Query language

New

MCP

For AI agents

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

1
2

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.

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.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

{
  "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.

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.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

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.

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.

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.

Currently v1Data refreshed realtime