Home

Welcome to the TOMP-API wiki!

This WIKI contains the lastest version of the TOMP-API. To facilitate the implementation of the API, we've made some supportive documentation with some examples/explanations. Not all scenario's are reflected in them, but they'll probably will be of value.

• Planning phase
• Booking phase
• Trip execution phase - start
• Trip execution phase - on route
• Trip execution phase - end
• Operator information
• Payment
• [Support]
• [General]

Implementation - how to's (Q&A)

• Simple Operator information
• Simple Planning phase
• Planning phase - multiple assets with one booking
• Transport operator with manual conformation / delegated confirmation of booking a leg
• Requesting deposits

Current version: 1.1.1

• illustrative document

Participants

• Cargaroo
• InTraffic/TURNN
• PAXX
• DAT.Mobility/Kyyti/GoOV
• CITYWAY
• GVB

Updates

1.1.2: more payment phase, but also include the first implementation impacts Includes:

• Operator information:
  1. missing available assets in operator information (#83)
• Planning options:
  1. overlays can now be handled in a composit-leg (#59)
  2. fare scales (#89)
• Payment:
  1. extra condititions for payment (upfront-payment and pay-when-finished) and optional bank account (#85)
  2. distance or time based scales (#87)
• some small adjustments:
  1. missing MP/TO id (#86)
  2. geojson to communicate the leg (reducing the message length) (#63)

1.1.1: goal: first set up for the payment phase (batch payment). Includes:

• payment phase
• 'Postponed commit' scenario
• Transport types clarified
• More precise description of travellers for more accurate planning
• return conditions
• some smaller issues:
  1. corrected example values
  2. merge 'mode' and 'type-of-asset'

1.1.0: major changes, not compatible with 1.0.0.
Includes now:

• planning phase
• booking phase
• trip execution phase
• REST implementation
• first setup webhooks
• first setup authentication
• one swaggerfile to maintain
• first setup TOMP API for dummies (WIKI)
• all kinds of smaller issues:
  1. adjustments on the availability check (timestamp, number of passangers, request of ID's, 'woordenboek reizigers'
  2. longitude/latitude is now everywhere in an object instead of array
  3. generic message header
  4. uniformity