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 " >Fleet calls Elife API to retrieve ride details.</p><p class="slate-p " >Fetches complete details of an existing ride including all trip segments and passenger information.</p><div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=info ><div class="callout-icon"><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p " >When the same field appears at both the ride level and the trip level, the trip‑level value is authoritative for that trip and the ride‑level value must be ignored. The ride‑level value should be treated only as a fallback / summary for the booking when no trip‑specific value is present.</p></div></div><p class="slate-p " ></p>

Fleet calls Elife API to retrieve ride details.

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

Authorization

Unique identifier for the ride to be updated

ride_id

Indicates if the operation was successful

success

vehicle_class

price

passenger_breakdown

amenities

passenger_count

luggage_count

driver_instruction

trips

reference

Unauthorized - invalid authentication credentials

<p class="slate-p " >Allows a supplier to cancel a ride they have previously accepted, providing a reason for the cancellation. The ride transitions to the CANCELLED status, the assignment is released, and the cancellation reason is recorded for downstream
</p><p class="slate-p " ></p>

Allows a supplier to cancel a ride they have previously accepted, providing a reason for the cancellation. The ride transitions to the CANCELLED status, the assignment is released, and the cancellation reason is recorded for downstream


Trip number within the ride (defaults to 1 for single‑leg rides).

trip_no

Free‑text reason explaining why the supplier is cancelling.

reason

Identifier of the accepted ride to cancel

data

<p class="slate-p " ></p><p class="slate-p " >Polling endpoint for suppliers to retrieve rides assigned or available to them, filtered by time window and status.</p><p class="slate-p " >Time window</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Ride‑hailing rides — set from_utc to “now” and omit to_utc. The endpoint returns rides eligible for immediate dispatch from this point onward.</div></li><li class="slate-li " ><div style="position:relative">Prebooking rides — provide both from_utc and to_utc as UNIX epoch timestamps to retrieve rides scheduled within that window.</div></li></ul><p class="slate-p " >Every ride is scoped at trip level</p><p class="slate-p " ></p><div class="published-table"><div class="table-container" style="padding-left: 0px;"><div class="published-table-header" style="width:100%;min-width:100%;"><div >Status</div><div >Description</div></div><table class="slate-table" style="min-width:100%;"><colgroup ><col style="width:initial"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><td class="slate-td"><p class="slate-p " >PENDING</p></td><td class="slate-td"><p class="slate-p " >Ride is available for the supplier to accept</p></td></tr><tr class="slate-tr " ><td class="slate-td"><p class="slate-p " >ACCEPTED</p></td><td class="slate-td"><p class="slate-p " >Ride has already been accepted by the supplier and is assigned to them</p></td></tr><tr class="slate-tr " ><td class="slate-td"><p class="slate-p " >CANCELLED</p></td><td class="slate-td"><p class="slate-p " >Ride was assigned to the supplier but has since been cancelled</p></td></tr></tbody></table></div></div><p class="slate-p " ></p>

Polling endpoint for suppliers to retrieve rides assigned or available to them, filtered by time window and status.

Status

Description

lower bound of the time window for the rides pickup time in utc unix timestamp

from_utc

status

upper bound of the time window for the rides pickup time in utc unix timestamp

to_utc

<p class="slate-p " ></p><p class="slate-p " >Suppliers calls Elife to  accept or reject the status of a dispatch. </p><p class="slate-p " >When accepting a ride‑hailing ride, the supplier must include the assigned driver and vehicle details in the same request. The acceptance will be rejected if these are missing. </p><p class="slate-p " >For prebooking rides, driver and vehicle details may be submitted later via the supplier callback once they are confirmed.</p>

Suppliers calls Elife to  accept or reject the status of a dispatch. 

When accepting a ride‑hailing ride, the supplier must include the assigned driver and vehicle details in the same request. The acceptance will be rejected if these are missing. 

For prebooking rides, driver and vehicle details may be submitted later via the supplier callback once they are confirmed.

Sequential number of the trip to be updated.
If not provided, the status applies to the entire ride.


Optional notes explaining the reason for acceptance or rejection.
Particularly useful when rejecting a ride.


notes

New status for the ride or trip:
- ACCEPTED: The fleet accepts the ride/trip and will service it
- REJECTED: The fleet cannot service the ride/trip


driver

vehicle

Unique identifier for the ride whose status needs to be updated

error

<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

Ask an AI

Code with AI