Geo Data time zone and local time API

Use the Geo Data time zone and local time API to retrieve time-zone information, local date and time and geographic position as structured JSON from Geo Data. Choose coordinates, longitude and search words as optional query conditions to select the source records or view required for your request. Use these results to resolve local clock information and account for time-zone changes when scheduling across locations. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.

Selected price
$0.002 / billing creditPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Optional parameters (10)
Latitude (-90 to 90). Pass with `lon`; or use `q`, `postal_code` or `geonameid` instead.
Longitude (-180 to 180).
Place name in any language, optionally with region and country: `Paris`, `Springfield, IL, US`, `München`. The most populous match wins (towns of 1,000+ people).
Postal code, with `country` (default US): `10001`, `SW1A 1AA` + `country=GB`.
Country for `q` or `postal_code`: ISO code (`US`, `GB`, `DE`) or English name.
0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
1 skips the 24-hour cache and fetches live.
JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON are not supported.
With output=csv|ndjson: the top-level list to turn into rows (e.g. `reviews`), or `.` for the whole object as one row.

Sample response

{
  "abbreviation": "GMT+9",
  "attribution": "Place data: GeoNames (geonames.org), CC BY 4.0",
  "cached": false,
  "credits_used": 1,
  "dst_offset": null,
  "fetched_at": "2026-11-19T12:26:41.894Z",
  "is_dst": false,
  "lat": 35.6762,
  "local_time": "2026-11-19T21:26:41+09:00",
  "location": {
    "admin1": "Tokyo",
    "admin1_code": "40",
    "admin2": "Suginami-ku",
    "ascii_name": "Eifuku",
    "country": "Japan",
    "country_code": "JP",
    "distance_km": 0.9,
    "elevation_m": 46,
    "feature": "section of a populated place",
    "feature_code": "PPLX",
    "geonameid": 8573723,
    "lat": 35.6755,
    "lon": 139.63992,
    "name": "Eifuku",
    "population": 15709,
    "timezone": "Asia/Tokyo"
  },
  "lon": 139.6503,
  "observes_dst": false,
  "query": {
    "lat": 35.6762,
    "lon": 139.6503
  },
  "standard_offset": "+09:00",
  "timezone": "Asia/Tokyo",
  "utc_offset": "+09:00",
  "utc_offset_minutes": 540,
  "utc_time": "2026-11-19T12:26:41Z"
}

Response result

Response structure

Inferred from examples
  • abbreviationstring
  • attributionstring
  • cachedboolean
  • credits_usedinteger
  • dst_offsetnull
  • fetched_atstring
  • is_dstboolean
  • latnumber
  • local_timestring
  • locationobject
    • admin1string
    • admin1_codestring
    • admin2string
    • ascii_namestring
    • countrystring
    • country_codestring
    • distance_kmnumber
    • elevation_minteger
    • featurestring
    • feature_codestring
    • geonameidinteger
    • latnumber
    • lonnumber
    • namestring
    • populationinteger
    • timezonestring
  • lonnumber
  • observes_dstboolean
  • queryobject
    • latnumber
    • lonnumber
  • standard_offsetstring
  • timezonestring
  • utc_offsetstring
  • utc_offset_minutesinteger
  • utc_timestring

Loading related APIs…

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Geo Data time zone and local time API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.