Elife

API for creating, updating, and managing ride information between customers and fleet services.
This API allows for booking transportation and managing ride details.

## Authentication
This API uses Basic Authentication. Use your fleet email as username and fleet login password as password.


Supplier Ride Management API (V3 Latest)

Authentication

Get an access token using client credentials

Obtain OAuth access token

Elife APIs

Fetches complete details of an existing ride including all trip segments
and passenger information.


Retrieve ride details

Cancel Accepted ride

GET my rides

Updates the status of a ride or specific trip to ACCEPTED or REJECTED.
This endpoint allows the fleet to indicate whether they can service the requested ride.


Accept or Reject a ride

Supplier Callbacks

Assigns driver and vehicle information to specific trips within a ride.
This endpoint allows the fleet to provide details about who will service the ride.


Provide driver and vehicle details

Updates the current status and location of a driver for a specific trip.
This endpoint is used to provide real-time updates about the driver's status.


Update driver events and location

Update Meeting Point Instruction

Supplier Webhooks

Ride Cancel notifcation

Available-rides notification

Updates details of an existing ride. Only include the fields you want to modify.
This endpoint can also be used to cancel a ride by changing the status to "CANCELLED".


Update an existing ride

Creates a new ride booking in the system with all the required details.
This endpoint is used to initiate a new ride request with the fleet service.


Dispatch ride to fleet

Existing Supplier Management API (V2)

Default

ELIFE & Supplier API's Latest Verson

Production

ELIFE API server

supplier API server

Sandbox

<p class="slate-p " >Elife provides a set of APIs for creating, updating, and managing ride dispatch information to our  supplier partners. The APIs help supplier partners fulfill ride orders from demand partners.</p><p class="slate-p " ></p><h4 class="slate-h4 " ><strong class="slate-bold">API Endpoint Allocation</strong></h4><p class="slate-p " >API endpoints are provided <strong class="slate-bold">per partner and per API</strong>, allowing Elife to manage computational resources based on each partner’s volume and specific implementation requirements.</p><p class="slate-p " ></p><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><h4 class="slate-h4 " ><strong class="slate-bold">Sandbox Environment</strong></h4><p class="slate-p " >A <strong class="slate-bold">sandbox environment</strong> is provisioned for each partner to support <strong class="slate-bold">development and testing</strong> before production deployment. Sandbox endpoints will be shared during the development phase.</p><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><p class="slate-p " ></p><p class="slate-p " ><strong class="slate-bold">Available APIs</strong></p><p class="slate-p " >The Supplier Ride Management API (V3) is the latest generation of Elife&apos;s two‑way integration surface with transportation suppliers. It is organised into four groups, plus a reference link to the legacy V2 API that some suppliers may still be running against.</p><p class="slate-p " ><strong class="slate-bold">Authentication</strong></p><p class="slate-p slate-indent-1" style="24px"><strong class="slate-bold">Obtain Oauth access token</strong>  API allows to Exchanges client credentials for a short‑lived access token. Both Elife and the supplier must implement this endpoint on their side, since the integration is mutually authenticated: Elife obtains a token from the supplier to deliver webhooks, and the supplier obtains a token from Elife to call Elife APIs.</p><p class="slate-p " ><strong class="slate-bold">Elife APIs</strong></p><p class="slate-p " >APIs that the supplier calls on Elife to read and act on rides assigned to them.</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Retrieve ride details API </strong> Returns the full detail of a single ride, including pickup/dropoff, passenger and luggage information, vehicle class, and current status.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Cancel Accepted Ride API </strong>Cancels a ride that the supplier had previously accepted, with a free‑text reason recorded for audit.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">GET My rides API</strong>  API allows supplier to retrieve all rides assigned or offered to them, filtered by a UTC time window and status (pending, accepted, cancelled). Supports both ride‑hailing and prebooking.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Accept or Reject ride API</strong> Allows supplier to respond to a ride assignment. Acceptance of a ride‑hailing ride must include the driver and vehicle details in the same request</div></li></ul><p class="slate-p " ><strong class="slate-bold">Supplier Webhooks</strong></p><p class="slate-p " >Server‑to‑server callbacks that Elife sends to the supplier&apos;s system to push state changes and new ride offers in real time.</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Dispatch ride to fleet </strong>Notifies the supplier of a new ride that has been dispatched to them.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Update an existing ride</strong> Notifies the supplier of changes to a previously dispatched ride (e.g. pickup time, location, passenger count).</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Available‑rides notification</strong> Pushes one or more new ride‑hailing rides that are available for the supplier to accept. No dispatch row is created on Elife&apos;s side until the supplier accepts the ride.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Ride Cancel notification</strong> Notifies the supplier that a previously accepted ride (prebooking or ride‑hailing) has been cancelled.</div></li></ul><p class="slate-p " ><strong class="slate-bold">Supplier Callbacks</strong></p><p class="slate-p " >Endpoints the supplier calls on Elife to report driver, vehicle, and trip progress information once a ride has been accepted.</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Provide driver and vehicle details </strong>Submits the assigned driver and vehicle information for a ride. Required as part of accepting a ride‑hailing ride; may also be sent post‑accept for prebooking rides.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Update driver events and location </strong>Streams driver status events and current GPS location during the ride lifecycle.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Update Meeting Point Instruction </strong>Updates the meeting‑point instruction shown to the passenger for shuttle transfers.</div></li></ul><p class="slate-p " ></p><p class="slate-p " ><a href="https://app.theneo.io/elifetransfer/elife-and-fleet-api-s/fleet-ride-management-api" target="">Existing v2 version of API&apos;s</a></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

Elife provides a set of APIs for creating, updating, and managing ride dispatch information to our  supplier partners. The APIs help supplier partners fulfill ride orders from demand partners.

, allowing Elife to manage computational resources based on each partner’s volume and specific implementation requirements.

 is provisioned for each partner to support 

 before production deployment. Sandbox endpoints will be shared during the development phase.

The Supplier Ride Management API (V3) is the latest generation of Elife's two‑way integration surface with transportation suppliers. It is organised into four groups, plus a reference link to the legacy V2 API that some suppliers may still be running against.

  API allows to Exchanges client credentials for a short‑lived access token. Both Elife and the supplier must implement this endpoint on their side, since the integration is mutually authenticated: Elife obtains a token from the supplier to deliver webhooks, and the supplier obtains a token from Elife to call Elife APIs.

APIs that the supplier calls on Elife to read and act on rides assigned to them.

Server‑to‑server callbacks that Elife sends to the supplier's system to push state changes and new ride offers in real time.

Endpoints the supplier calls on Elife to report driver, vehicle, and trip progress information once a ride has been accepted.

<p class="slate-p " >APIs that the supplier calls on Elife to read and act on rides assigned to them.</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Retrieve ride details API </strong> Returns the full detail of a single ride, including pickup/dropoff, passenger and luggage information, vehicle class, and current status.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Cancel Accepted Ride API </strong>Cancels a ride that the supplier had previously accepted, with a free‑text reason recorded for audit.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">GET My rides API</strong>  API allows supplier to retrieve all rides assigned or offered to them, filtered by a UTC time window and status (pending, accepted, cancelled). Supports both ride‑hailing and prebooking.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Accept or Reject ride API</strong> Allows supplier to respond to a ride assignment. Acceptance of a ride‑hailing ride must include the driver and vehicle details in the same request</div></li></ul><p class="slate-p " ></p>

<p class="slate-p " >Endpoints the supplier calls on Elife to report driver, vehicle, and trip progress information once a ride has been accepted.</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Provide driver and vehicle details </strong>Submits the assigned driver and vehicle information for a ride. Required as part of accepting a ride‑hailing ride; may also be sent post‑accept for prebooking rides.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Update driver events and location </strong>Streams driver status events and current GPS location during the ride lifecycle.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Update Meeting Point Instruction </strong>Updates the meeting‑point instruction shown to the passenger for shuttle transfers.</div></li></ul><p class="slate-p " ></p>

<p class="slate-p " >Server‑to‑server callbacks that Elife sends to the supplier&apos;s system to push state changes and new ride offers in real time.</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Dispatch ride to fleet </strong>Notifies the supplier of a new ride that has been dispatched to them.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Update an existing ride</strong> Notifies the supplier of changes to a previously dispatched ride (e.g. pickup time, location, passenger count).</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Available‑rides notification</strong> Pushes one or more new ride‑hailing rides that are available for the supplier to accept. No dispatch row is created on Elife&apos;s side until the supplier accepts the ride.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Ride Cancel notification</strong> Notifies the supplier that a previously accepted ride (prebooking or ride‑hailing) has been cancelled.</div></li></ul><p class="slate-p " ></p>

Sections