onde

Use case

The city picker that returns the time zone

When an organizer picks a city, the same result carries its time zone. Store it with the event and show the correct start time to every attendee, with no second lookup.

30,000 requests a month free, with commercial use. No card needed.

Live API

Type a city. Each result in the response carries its time zone.

Autocomplete /v1/cities/autocomplete
curl "https://api.onde.earth/v1/cities/autocomplete?q=kyoto" \
  -H "Authorization: Bearer $ONDE_KEY"
Response Example
{
  "data": [
    {
      "id": "city_39sy1dm2dj",
      "name": "Kyoto",
      "localName": "京都市",
      "type": "city",
      "parentCityId": null,
      "country": {
        "code": "JP",
        "name": "Japan"
      },
      "region": {
        "id": "region_yjwfrtj0fe",
        "isoCode": "JP-26",
        "name": "Kyoto"
      },
      "coordinates": {
        "latitude": 35.02107,
        "longitude": 135.75385
      },
      "population": 1463723,
      "timeZone": "Asia/Tokyo",
      "isCapital": false,
      "disputed": false,
      "match": "exact"
    }
  ],
  "meta": {
    "dataset": "2026-11-17"
  }
}

One wrong time zone and people miss the start

A start time is only correct in the time zone of the event. Get it wrong, and attendees arrive an hour late and write to your support team.

Questions

Is the time zone right for every venue?
It is the time zone of the city. Close to a zone border, a venue can be in a different zone.
Does Onde store venue addresses?
No. Onde gives you the city. Keep venue addresses in your own data.
What counts as a request?
Each suggestion list, city lookup, and location lookup counts one request, at one price.

Get the time zone with every city

Create a key, add the field to your event form, and store the time zone with each event.

  • No card needed
  • 30,000 requests a month free
  • Commercial use on the Free plan
  • Store every result for good
  • Public key locked to your domains