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

Authentication

Get an access token using client credentials

Obtain OAuth access token from supplier

Rides

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

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


Retrieve ride details (Phase 2)

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

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 (Phase 2)

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

Default

ELIFE & Supplier API's

Production

ELIFE API server

supplier API server

Sandbox

API for creating, updating, and managing ride information between customers and supplier services.
This API allows for booking transportation and managing ride details.<h2 class="slate-h2 " >Authentication</h2>This API uses Basic Authentication. Use your supplier email as username and supplier login password as password.

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

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

Elife calls into the fleet management system through this API that serve functions to send new rides that are assigned/dispatched to the fleet.

Elife calls into the fleet management system through this API that serve functions to send new rides that are assigned/dispatched to the fleet.

Unique identifier for the ride, used for tracking and reference

ride_id

Number of vehicles required for this booking

vehicle_count

vehicle_class

price

passenger_breakdown

amenities

Total number of passengers (must match sum of all passenger types in passenger_breakdown)

passenger_count

Total number of luggage pieces for all passengers

luggage_count

Special instructions for the driver regarding the overall ride

driver_instruction

List of trip segments that make up the complete ride

trips

Authorization

Indicates if the operation was successful

success

error

Unauthorized - invalid authentication credentials

code

message

Fleet calls Elife API to retrieve ride details.Fetches complete details of an existing ride including all trip segments and passenger information.

Fleet calls Elife API to retrieve ride details.

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

Unique identifier for the ride to be updated

reference

Elife calls Fleet API to update ride details.Updates details of an existing ride, include the updated ride details.

Elife calls Fleet API to update ride details.

Updates details of an existing ride, include the updated ride details.

passenger

Updated special instructions for the driver

Updated list of trip segments. Include only the trips you want to update.
Each trip must include trip_no to identify which trip to modify.


Fleet calls Elife API to upadte the dispatch status.Updates the status of a ride or specific trip to ACCEPTED or REJECTED.

Fleet calls Elife API to upadte the dispatch status.

Updates the status of a ride or specific trip to ACCEPTED or REJECTED.

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


trip_no

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


status

Unique identifier for the ride whose status needs to be updated

Sections