1. Home
  2. Business
  3. 9292 Vertrektijden API

Business

9292 Vertrektijden API

Information about every public transport stop in the Netherlands

Looking for a public transport service in the vicinity or within a specific region? Want to know which services are available at a stop and when they depart? The Vertrektijden API delivers that information for all public transport services in the Netherlands, including information about the occupancy of services, delays, disruptions and any scheduled or unscheduled changes in the regular services. Notices and comments of operators are included for each departure to inform travellers of relevant information they should know before departure.

What is the difference with the Vertrekwijzer?

The Vertrekwijzer delivers information about a predefined set of public transport stops. This is intended to be displayed on wall mounted screens at entrances or central areas in schools and offices. The Vertrektijden API delivers information about any stop and provides facilities to search for public services. The information about services is more elaborate and aimed to be used in Apps or interactive websites or by content providers that deliver regional information about public transport services.

How to use the Vertrektijden API?

The Vertrektijden API can be used in 2 different ways :

  1. Searching for public service stops in a geografical area or by using keywords
  2. Requesting departure information of stops that are found or selected

Searching for public transport stops

There are different ways to search for stops:

  1. Within a circular area, specified by center coordinates in RDM or WGS84 and a radius in meters
  2. Within a rectangular area, specified by the corner coordinates in RDM or WGS84
  3. Using keywords that correspond to the names of stops or the streets or places where stops are located. Names can be partial and can be combined to increase accuracy.

This results in a list of stops that meets the search criteria. The following information is delivered per stop:

  • Name and place of the stop
  • Information about the lines that are currently serviced at the stop
  • Accessiblity of the stop for physically impaired persons
  • Textual messages of operators about the stop, e.g. if services are suspended due to road construction works
  • Geographical coordinates of the location of the stop (in RDM or WGS84)
  • The operator that manages the stop
  • An identification of the stop that can be used to request departure information or refesh information about selected stops in case information could have been changed

When stops are returned within a geographical area, they are sorted by distance to the center of the search area. So the stops nearest to the center are listed first.

4 types of stops

When searching for stops, the type of stop can be selected. 9292 can deliver information about 4 types of stops:

  1. Physical stops that are registered by 9292
  2. Cluster stops that are registered by 9292 (one or more physical stops can be combined in a cluster stop when they are identified by the same name, e.g. the stops on different sides of a road)
  3. Quay stops that are registered in the CHB (Centraal Halte Bestand) - comparable with physical stops
  4. StopPlaces that are registered in the CHB - comparable with cluster stops

These types of stops are linked to each other and linking data can be delivered if requested.

Requesting departure information

After public transport stops have been found or selected, the details of departing services can be requested for any number of stops by listing their identification. In each request, a period is specified for which the departing services will be returned. Normally, this period will start at the moment the request is made, but it can be any moment on the current day and the next few days. Delays or disruptions will be included when they are known at the moment the request is received. The departure information is grouped and sorted chronologically per stop. For each departure, the following information is returned:

  • The scheduled and expected time of departure
  • The destination
  • Status of the service (delayed, early, added, cancelled, ...)
  • The deviation to the scheduled time of departure in seconds
  • Scheduled platform of departure
  • Changed platform of departure
  • Occupancy during departure
  • Modality of the service
  • Transport type of the service
  • Accessibility of the service for physically impaired persons
  • Identification of the line
  • Indication of the first and last service for a line on the current day
  • Operator that provides the service
  • General notice messages for the service (e.g. a temporary suspension during school holidays or a phone number to request a service)
  • Other messages about disruptions or services that replace a scheduled service

The departure information can be filtered for specified operators, lines or transport types, e.g. only bus services of a particular operator can be requested.

It is also possible to request arrival information of services. Optionally, information can be included of flexible public transport, e.g. BelBus.

More information

There is Swaggerdocumentation available for more technical details of the Vertrektijden API. This can be found at https://vertrektijden-api.9292.nl. The following link also provides more information about the use of the Vertrektijden.

Any remaining questions?

Do you have any remaining questions, or would you like to try the Vertrektijden API for a while? Call our Servicedesk at +31 88 - 07660620 or send an email to servicedesk@9292.nl