Journey search backend APIs

This section describes backend endpoints that are provided by Mileus and required from the RH operator.

Mileus APIs

For all endpoints the RH operator needs to provide their API key in the api-key header.

/auth/v1/token

Authentication endpoint, used for retrieving the auth token by RH backend which is then passed to the RH frontend app so that the app could communicate with Mileus backend securely.

/search/v1/start/match-drivers

Journey search start endpoint, called when the RH operator wants to retrieve intermodal journey matches for a given route.

/journeys/v1/taxi-offer

Endpoint for RH operator to let Mileus know that there is a taxi offer available for the passenger's requested journey. The request should contain details about the offer (driver, car, price) and Mileus stores this information to be used by the passenger later.

RH operator APIs

Order accept API

Mileus calls this API when the order is accepted from the passenger side which is the final confirmation that the ride is going to happen.

Order cancel API

Mileus calls this API whenever the order in the RH operator system needs to be canceled from the passenger side, so the ride shouldn't happen and the driver should be notified.