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.

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.

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.

driver

vehicle

meeting point instruction for the passenger

meeting_point

trips

Authorization

Unique identifier for the ride to assign driver details

ride_id

success

error

Unauthorized - invalid authentication credentials

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.

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.

Sequential number of the trip the status update applies to

trip_no

status

points

Unique identifier for the ride to update driver status

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.

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. 

trip number of the itinerary, for a round trip its trip number is 1  for onward journey and 2 for return journey

Sections