Data updates
Copy link

We update each country's data about once a month. This page explains how to check the date of the data you are reading, and what changes between updates.

Check the data date
Copy link

updated_at is the date of a dataset's data in a country. GET /v1/catalog/{country} returns it for every dataset, with its number of records.

Request

curl -H "X-Application-Id: YOUR_APP_ID" -H "X-Api-Key: YOUR_APP_KEY" \
  "https://data.traveltimeapp.com/v1/catalog/gb"

Response

{
  "country": { "id": "gb", "name": "United Kingdom", "…": "…" },
  "results": [
    {
      "id": "places",
      "countries": {
        "gb": { "available": true, "updated_at": "2026-10-18", "records": 4710961, "…": "…" }
      },
      "…": "…"
    },
    {
      "id": "transit-stations",
      "countries": {
        "gb": { "available": true, "updated_at": "2026-10-17", "records": 326290, "…": "…" }
      },
      "…": "…"
    },
    "… 8 more datasets"
  ],
  "…": "…"
}

Each dataset has its own updated_at. It is null when there is no date, for example for a dataset the country does not have. Treat a null date as unknown. On a single place, updated_at is the date Foursquare last refreshed its record. A place Foursquare does not list gets its last OpenStreetMap edit, a place only a public register lists gets the date we loaded it, and a place only Overture or TravelTime lists gets null. The rest of the response is on Catalog and categories.

How often data updates
Copy link

We update each country about once a month. An update replaces a whole dataset, so you never see a mix of old and new data. Between updates the data does not change, so the same request returns the same response.

What changes between updates
Copy link

  • Places. New places are added and closed places are removed. The number of places moves by about 0.5% to 2% a month. A place's listed_by, verified and verified_by can change when a source or register adds or drops it. A place listed by two sources can become a one-source place, which can take it out of the Places routes. On /v1/places, min_sources=1 keeps it. See Places.
  • Public transport. Station counts rarely change. A new line or station shows up in the update after it opens. Frequencies change when seasonal timetables start.
  • Open spaces. Open space outlines change slowly.

Place ids change between updates
Copy link

We make new place ids (pl_) at each monthly update, so a place id you store stops working after the next update. Store the place's name and coordinate instead, or look the place up again when the places dataset's updated_at moves.

All other ids stay the same between updates:

  • Stations (st_). The id is made from the country, the mode, the name and the position, so it stays the same while those do.
  • Lines (ln_). The id is made from the country, the operator and the line's name, so it stays the same while those do.
  • Roads (rd_). The id is made from the road's ref, such as M1, or its name when it has no ref, and its direction. A road entry or exit (ra_) takes its id from the Overture id of the point where the ramp meets the local road.
  • Open spaces (os_). The id is Overture's id, so it stays the same for as long as Overture keeps it.
  • Boundaries (gb-camden). The id is made from names, so it stays the same while the boundary and its name do.

Caching and data dates
Copy link

We recommend that you key the cache for each dataset on its own updated_at. Read the value once and keep it, then refresh your cache when a later GET /v1/catalog/{country} response shows a new value. Do not poll for it, as it changes about once a month.

The data routes and GET /v1/catalog/{country} send no Cache-Control and no ETag, so cache their responses at your own TTL. GET /v1/categories and GET /v1/catalog are fresh for 1 hour; GET /v1/catalog also sets a weak ETag.

If you show the data to your users, show its updated_at date too.