ELIFE & Supplier API's Latest Verson

## Sections
• [Supplier Ride Management API (V3 Latest)](https://developer.elifelimo.com/suppliers/fleet-ride-management-api.md): 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. API Endpoint Allocation API endpoints are provided per partner and per API , allowing Elife to manage computational resources based on each partner’s volume and specific implementation requirements. Sandbox Environment A sandbox environment is provisioned for each partner to support development and testing before production deployment. Sandbox endpoints will be shared during the development phase. Available APIs 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. Authentication Obtain Oauth access token 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. Elife APIs APIs that the supplier calls on Elife to read and act on rides assigned to them. Retrieve ride details API Returns the full detail of a single ride, including pickup/dropoff, passenger and luggage information, vehicle class, and current status. Cancel Accepted Ride API Cancels a ride that the supplier had previously accepted, with a free‑text reason recorded for audit. GET My rides API 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. Accept or Reject ride API 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 Supplier Webhooks Server‑to‑server callbacks that Elife sends to the supplier's system to push state changes and new ride offers in real time. Dispatch ride to fleet Notifies the supplier of a new ride that has been dispatched to them. Update an existing ride Notifies the supplier of changes to a previously dispatched ride (e.g. pickup time, location, passenger count). Available‑rides notification Pushes one or more new ride‑hailing rides that are available for the supplier to accept. No dispatch row is created on Elife's side until the supplier accepts the ride. Ride Cancel notification Notifies the supplier that a previously accepted ride (prebooking or ride‑hailing) has been cancelled. Supplier Callbacks Endpoints the supplier calls on Elife to report driver, vehicle, and trip progress information once a ride has been accepted. Provide driver and vehicle details 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. Update driver events and location Streams driver status events and current GPS location during the ride lifecycle. Update Meeting Point Instruction Updates the meeting‑point instruction shown to the passenger for shuttle transfers. Existing v2 version of API's
• [Obtain OAuth access token](https://developer.elifelimo.com/suppliers/authentication/obtain-oauth-access-token.md): This endpoint must be implemented on both the Elife and supplier sides. Before either party calls any other endpoint on the other system, it first authenticates against this endpoint to obtain a short‑lived OAuth access token, which is then presented in the Authorization header of subsequent requests. This establishes a symmetric, mutually‑authenticated integration: the supplier obtains a token from Elife in order to call Elife APIs, and Elife obtains a token from the supplier in order to deliver webhooks and other server‑to‑server callbacks. Same as V2
• [Elife APIs](https://developer.elifelimo.com/suppliers/rides.md): APIs that the supplier calls on Elife to read and act on rides assigned to them. Retrieve ride details API Returns the full detail of a single ride, including pickup/dropoff, passenger and luggage information, vehicle class, and current status. Cancel Accepted Ride API Cancels a ride that the supplier had previously accepted, with a free‑text reason recorded for audit. GET My rides API 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. Accept or Reject ride API 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
  • [Retrieve ride details](https://developer.elifelimo.com/suppliers/rides/retrieve-ride-details.md): Fleet calls Elife API to retrieve ride details. Fetches complete details of an existing ride including all trip segments and passenger information. 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.
  • [Cancel Accepted ride](https://developer.elifelimo.com/suppliers/rides/cancel-accepted-ride.md): 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
  • [GET my rides](https://developer.elifelimo.com/suppliers/rides/retrieve-all-available-ride-hailing-rides-for-the-fleet.md): Polling endpoint for suppliers to retrieve rides assigned or available to them, filtered by time window and status. Time window Ride‑hailing rides — set from_utc to “now” and omit to_utc. The endpoint returns rides eligible for immediate dispatch from this point onward. Prebooking rides — provide both from_utc and to_utc as UNIX epoch timestamps to retrieve rides scheduled within that window. Every ride is scoped at trip level Status Description PENDING Ride is available for the supplier to accept ACCEPTED Ride has already been accepted by the supplier and is assigned to them CANCELLED Ride was assigned to the supplier but has since been cancelled
  • [Accept or Reject a ride](https://developer.elifelimo.com/suppliers/rides/accept-or-reject-a-ride.md): 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.
• [Supplier Callbacks](https://developer.elifelimo.com/suppliers/drivers.md): Endpoints the supplier calls on Elife to report driver, vehicle, and trip progress information once a ride has been accepted. Provide driver and vehicle details 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. Update driver events and location Streams driver status events and current GPS location during the ride lifecycle. Update Meeting Point Instruction Updates the meeting‑point instruction shown to the passenger for shuttle transfers.
  • [Provide driver and vehicle details](https://developer.elifelimo.com/suppliers/drivers/provide-driver-and-vehicle-details.md): Fleet calls Elife fleet api to update driver and vehicle details. 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. Same as V2
  • [Update driver events and location](https://developer.elifelimo.com/suppliers/drivers/update-driver-status-and-location.md): Fleet calls Elife api to post driver events and update location. We only use the data if driver waited for the correct amount of the waiting time. Fleet should not call more than once per minute per ride if the status does not change and location should be at least 10 seconds apart. RECOMMENDATION: take location every 10 seconds and send it every minute with 6 points. Same as V2
  • [Update Meeting Point Instruction](https://developer.elifelimo.com/suppliers/drivers/update-meeting-point-instruction.md): Fleet calls Elife API to send the meeting point for a given trip for a ride. This is useful when the driver cannot reach the default pickup point and needs to coordinate a nearby meeting location. The meeting point can be specified as a lat, lng coordinate or a detailed instructions specifing the meeting point location. Allowed to provide meeting points only for shuttle rides. Same as V2
• [Supplier Webhooks](https://developer.elifelimo.com/suppliers/supplier-webhooks.md): Server‑to‑server callbacks that Elife sends to the supplier's system to push state changes and new ride offers in real time. Dispatch ride to fleet Notifies the supplier of a new ride that has been dispatched to them. Update an existing ride Notifies the supplier of changes to a previously dispatched ride (e.g. pickup time, location, passenger count). Available‑rides notification Pushes one or more new ride‑hailing rides that are available for the supplier to accept. No dispatch row is created on Elife's side until the supplier accepts the ride. Ride Cancel notification Notifies the supplier that a previously accepted ride (prebooking or ride‑hailing) has been cancelled.
  • [Ride Cancel notifcation](https://developer.elifelimo.com/suppliers/supplier-webhooks/send-ride-cancel-notifcation.md): Webhook sent from Elife to the supplier system to notify them that a previously accepted ride — either a prebooking or a ride‑hailing ride — has been cancelled in the Elife system.
  • [Available-rides notification](https://developer.elifelimo.com/suppliers/supplier-webhooks/send-available-ride-notification.md): Webhook sent from Elife to the supplier system to notify them of new incoming ride‑hailing rides that are available for acceptance. Each event may carry one or more rides; The supplier is expected to evaluate the payload and accept any rides they wish to fulfil .
  • [Update an existing ride](https://developer.elifelimo.com/suppliers/supplier-webhooks/update-an-existing-ride.md): Elife calls Fleet API to update ride details. Updates details of an existing ride, include the updated ride details. 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.
  • [Dispatch ride to fleet](https://developer.elifelimo.com/suppliers/supplier-webhooks/create-a-new-ride.md): Elife calls into the fleet management system through this API that serve functions to send new rides that are assigned/dispatched to the fleet. trip level information will always override the top level information 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.