Public transport API

Optima Public Transport (PuT) ETA provides advanced functions to handle several elements of the PuT data model:

• Lines
• Streets (associated to Put lines)
• Trips
• Stop locations
• PuT events

The PuT endpoints are based on the General Transit Feed Specification (GTFS), a data specification used by thousands of public transport providers.

Important:  Optima handles GTFS input packets compliant with either GTFS 1.0 and 2.0. The output is compliant with GTFS 1.0, without any data losses with respect to GTFS 2.0.

The available endpoints can be combined to build several workflows.

Here is a non-exhaustive list of three distinct workflows:

Trip management workflow

1. Getting all PuT events:

   → Getting PuT events

2. Getting the Estimated Time of Arrival (ETA) for a specific trip:

   → Getting the ETA for trips

3. Getting information on all events that have an effect on a specific trip:

   → Getting information on disruptions of a trip

4. Disabling a specific trip (according to information resulting from the previous step):

   → Disabling a trip

Stop management workflow

1. Getting all PuT events:

   → Getting PuT events

2. Getting the Estimated Time of Arrival (ETA) for a specific stop:

   → Getting the ETA for stops

3. Disabling a specific stop:

   → Disabling stops of a trip

Vehicle management workflow

1. Getting the Estimated Time of Arrival (ETA) for a specific trip:

   → Getting the ETA for trips

2. Getting information on all events that have an effect on a specific trip:

   → Getting information on disruptions of a trip

3. Getting the position of all vehicles involved in a specific trip, at a specific time:

   → Getting expected positions of vehicles by trips and time

Topics in this section