API – stationary ticket machines

Information about stationary ticket machines.

  • Endpoint: GET https://rozklad.renegades.at/api/v1/ticket-machines
  • Data type: application/json
  • Update frequency: as required

Data structure

{
  "data": [
    {
      "id": 1,
      "location": "aleja Powstańców Wielkopolskich",
      "latitude": 53.406796,
      "longitude": 14.528817,
      "payment_methods": {
        "cards": true,
        "coins": true,
        "banknotes": true
      },
      "updated_at": "2023-05-19T19:38:56.000000Z"
    },

    ...

  ]
}
  • int id – ticket machine identifier
  • string location – description of the ticket machine’s location
  • float latitude – geographic latitude of the ticket machine
  • float longitude – geographic longitude of the ticket machine
  • Added object payment_methods – payment methods available in the ticket machine
    • bool cards – accepts payment by card
    • bool coins – accepts payment by coins
    • bool banknotes – accepts payment by banknotes
  • string updated_at – timestamp of the last data update

General information

  1. The data are provided free of charge under the CC0 1.0 licence, for use in any context, with no prior notification required.
  2. Zarząd Dróg i Transportu Miejskiego w Szczecinie (Roads and Public Transport Authority in Szczecin) does not guarantee the accuracy or completeness of the data and accepts no liability for any loss or decisions made on the basis of this information.
  3. In any product using the data (application, website, publication, etc.), please cite the data source as Zarząd Dróg i Transportu Miejskiego w Szczecinie, or in abbreviated form, ZDiTM Szczecin; although not legally required, this is appreciated.
  4. Where possible, please include a link to this page or to the ZDiTM Szczecin homepage in any product using the data; this is also not a legal obligation.
  5. Clients should recognise and honour the HTTP headers Cache-Control and ETag.
  6. API requests are rate‑limited: 100 requests per minute per IP address across all endpoints. The X-RateLimit-Remaining header shows the number of remaining requests. Once the limit is reached, an HTTP 429 response is returned. The X-RateLimit-Reset header then contains a Unix timestamp for when the limit resets, and the Retry-After header shows the number of seconds until reset.
  7. If possible, please include in your User-Agent header information identifying the entity using the data (e.g. the name of your application, website, or its URL).
  8. In the event of excessive server load, ZDiTM Szczecin reserves the right to partially or fully block access to the API.