World Time API

Overview

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/worldtime

Example

How to call the World Time API in different programming languages.

curl -X GET \
  "https://api.apiverve.com/v1/worldtime?city=San%20Francisco" \
  -H "X-API-Key: your_api_key_here"

const response = await fetch('https://api.apiverve.com/v1/worldtime?city=San%20Francisco', {
  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?city=San%20Francisco', 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/worldtime?city=San%20Francisco", 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": {
    "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"
      }
    ]
  }
}

Authentication

The World Time API requires authentication via API key. Include your API key in the request header:

X-API-Key: your_api_key_here

Learn more about authentication →

Interactive 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:

Response

The World Time 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>
    <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

Response Structure

All API responses follow a consistent structure with the following fields:

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

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 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/graphql

query {
  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 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

World Time 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 World Time 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 World Time

Official World Time packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

JitPack

No-Code Integrations

World Time works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →

Zapier

Make

Pipedream

n8n

Power Automate

Frequently Asked Questions

People who used this also used...

Based on your interest in World Time, you might also like these APIs:

ZIP Demographics

ZIP Demographics provides detailed demographic data for any US ZIP code including population, income, education, housing, employment, and racial composition from the US Census American Community Survey.

5 credits per call

Unicode Character Lookup

Unicode Character Lookup is a tool for retrieving detailed information about Unicode characters. It provides codepoint, UTF-16 encoding, category, and emoji name information.

1 credit per call

Timezone Lookup

Timezone Lookup is a simple tool for looking up timezone data. It returns the timezone name, offset, and more.

1 credit per call