Rentlz Booking Management API

Created by Moveinsync Help, Modified on Sun, 27 Apr at 9:29 PM by Moveinsync Help

POSTVendor Acceptance

https://api.moveinsync.com/integration/{{Client BUID}}/rentlz/booking/status

This API handles the response for booking acceptance or rejection. It allows the system to update the status of a booking based on the user's decision. The status of the booking can be updated to either accept or deny the booking request.

Status can have the following values:

ACCEPT: Indicates that the booking has been accepted.
DENY: Indicates that the booking has been rejected.

HEADERS

Authorization

Bearer {{access_token}}

Bodyraw (json)

{
  "bookingId": "{{MoveInSync BookingID}}",
  "status": "{{Acceptance Status}}",
  "reason": "{{Reason for rejection}}"
}

POSTCab Driver Allocation

https://api.moveinsync.com/integration/{{Client BUID}}/rentlz/booking/assign/cab-driver

This API allows the vendor to send the cab and driver details assigned to a specific booking. The provided information includes the booking ID, the registration number of the cab, the driver's name and mobile number, as well as the type of cab assigned. This ensures that the system receives accurate details about the cab and driver to further transmit this information to the riders.

HEADERS

Authorization

Bearer {{access_token}}

Bodyraw (json)

{
  "bookingId": "{{MoveInSync BookingID}}",
  "cabRegNo": "{{Vehicle Registration Number}}",
  "driverName": "{{Driver Name}}",
  "driverMobile": "{{Driver Phone Number}}",
  "cabType": "{{Predefined Vehicle Type}}"
}

POSTOTP

https://api.moveinsync.com/integration/{{Client BUID}}/rentlz/booking/otp

This API is used to submit OTPs associated with a booking to verify check-in and check-out events. It accepts both Sign-In and Sign-Out OTPs for a given booking. In cases where only a single OTP is used for both events, the same value should be provided for both signInOtp and signOutOtp

bookingId is the unique identifier for the booking in the MoveInSync system.
signInOtp is the OTP used to verify the start of the trip.
signOutOtp is the OTP used to verify the end of the trip.
If the same OTP is used for both sign-in and sign-out, repeat the same value in both fields.

HEADERS

Authorization

Bearer {{access_token}}

Bodyraw (json)

{
  "bookingId": "{{MoveInSync BookingID}}",
  "signInOtp": "{{Sign In OTP}}",
  "singOutOtp": "{Sign Out OTP}}"
}

POSTDuty-Trip Details

https://api.moveinsync.com/integration/{{Client BUID}}/rentlz/booking/start-end

This API is used to log a driver-related event (such as duty start/end or trip start/end) for a given booking. Each event submission includes the location coordinates and timestamp of when the event occurred.

Field Details:

bookingId: Unique identifier for the booking in the MoveInSync system.
lat: Latitude where the event was recorded.
lang: Longitude where the event was recorded.
time: Timestamp of the event in epoch milliseconds.
eventName: Name of the event being logged. Must be one of the following:
- startDuty
- startTrip
- endTrip
- endDuty

Notes:

The API ensures accurate tracking of a driver's duty and trip lifecycle.
Make sure the eventName matches one of the allowed values to avoid validation errors.
time should be sent in epoch milliseconds format (e.g., 1713703420000).

HEADERS

Authorization

Bearer {{access_token}}

Bodyraw (json)

{
  "bookingId": "{{MoveInSync BookingID}}",
  "lat": "{{Latitude Geocord}}",
  "lang": "{{Longitude Geocord}}",
  "time": {{Event Time}},
  "eventName": "{{Event Name}}"
}

POSTTracking

https://api.moveinsync.com/integration/{{Client BUID}}/rentlz/booking/track

This API is used to send real-time tracking updates for a booking, including vehicle location, movement data (bearing, speed, accuracy), and event type. This enables precise monitoring of the vehicle throughout its journey.

Field Details:

bookingId: Unique identifier of the booking.
mBearing: Direction in degrees the vehicle is moving.
mSpeed: Speed of the vehicle (usually in m/s or km/h).
mStep: Motion step or change in movement (custom logic defined by client, optional meaning).
mAccuracy: Accuracy of the geolocation coordinates (in meters).
type: Type of tracking event. Must be one of:
- dispatch: Driver starts from the garage to reach the pickup point.
- arrived: Cab has arrived at the pickup location.
- pickup: Ongoing trip between pickup and drop point.
- drop: Cab has reached the final drop/destination.
time: Epoch time in milliseconds when the data was captured.
latitude: Latitude coordinate of the vehicle.
longitude: Longitude coordinate of the vehicle.

HEADERS

Authorization

Bearer {{access_token}}

Bodyraw (json)

{
  "bookingId": "{{MoveInSync Booking ID}}",
  "mBearing": {{Bearing}},
  "mSpeed": {{Speed}},
  "mStep": {{Step}},
  "mAccuracy": {{Accuracy}},
  "type": "{{Type}}",
  "time": {{Time}},
  "latitude": {{Latitude Geocord}},
  "longitude": {{Longitude Geocord}}
}