Multiple rider sign in/out vendor integration booking document

Booking Lifecycle & Operational APIs

This document defines the complete set of APIs required for integration between the vendor platform and the MoveInSync Rentlz platform. It covers the complete booking lifecycle flow  from booking creation to trip completion and invoicing.

End-to-End Booking Lifecycle Flow

The following sequence defines the recommended order in which APIs should be triggered during the lifecycle of a booking.

Note: Select the appropriate base URL (.com or .in) based on the customer's site URL.

Scenario 1: If the customer site URL is https://abcd.moveinsync.com/IND/login, use the following base URL: https://api.moveinsync.com

Scenario 2: If the customer site URL is https://efgh.moveinsync.in/IND/login, use the following base URL: https://api.moveinsync.in

? Base URL

1)  https://api.moveinsync.com

2)  https://api.moveinsync.in

? Authentication

All APIs require Bearer Token authentication.

Header:

Authorization: Bearer <access_token>

Content-Type: application/json

 1. POST OTP API

Endpoint

https://api.moveinsync.com/integration/{client-id}/rentlz/booking/v2/otp
or
https://api.moveinsync.in/integration/{client-id}/rentlz/booking/v2/otp

Description

This API is used to submit OTPs associated with a booking to verify check-in (Sign-In) and check-out (Sign-Out) events.

• Both signInOtp and signOutOtp must be provided.

• If the same OTP is used for both events, pass the same value in both fields.

• OTP must be sent separately for each rider.

Field Details

Request Body

[

  {

    "bookingId": "BLR-XXXX-XXXX-XOBB",

    "signInOtp": "1234",

    "signOutOtp": "6789",

    "uniqueRiderEmail": "rider1@gmail.com",

    "client": "pwcindia-PWCINDIA"

  },

  {

    "bookingId": "BLR-XXXX-XXXX-XO1BB",

    "signInOtp": "1234",

    "signOutOtp": "5678",

    "uniqueRiderEmail": "rider2@gmail.com",

    "client": "gs2-UAT"

  }

]

Sample Curl

POST
 'https://api.moveinsync.com/integration/{client-id}/rentlz/booking/v2/otp '
or
 'https://api.moveinsync.in/integration/{client-id}/rentlz/booking/v2/otp '

--header 'Authorization: Bearer <Your token>'

--header 'Content-Type: application/json'

--body '[

  {

    "bookingId": "BLR-XXXX-XXXX-XOBB",

    "signInOtp": "1234",

    "signOutOtp": "6789",

    "uniqueRiderEmail": "rider1@gmail.com",

    "client": "gs2-UAT"

  }

]'

Notes

• Same OTP can be reused for both fields if applicable.

• Each rider must have a separate entry.

? 2. POST Duty-Trip Details API

Endpoint

https://api.moveinsync.com/integration/{client-id}/rentlz/booking/start-end
or
https://api.moveinsync.in/integration/{client-id}/rentlz/booking/start-end

Description

This API is used to log driver-related events such as duty start/end and trip start/end for a given booking.

Each event includes:

• Location coordinates

• Timestamp

• Event type

Field Details

Allowed eventName Values

• startDuty

• startTrip

• endTrip

• endDuty

Request Body (Sample)

{

  "bookingId": "BLR-XXXX-XXXX-XOBB",

  "lat": "22.6211559",

  "lang": "88.4324648",

  "time": 1713703420000,

  "eventName": "startTrip"

}

Notes

• eventName must match one of the allowed values.

• time must be in epoch milliseconds format.

3. POST Attendance API

Endpoint

https://api.moveinsync.com/integration/{client-id}/rentlz/booking/attendance
or
https://api.moveinsync.in/integration/{client-id}/rentlz/booking/attendance

Description

This API is used to log employee events such as:

• SIGNIN

• SIGNOUT

• NOSHOW

Each request includes booking details, rider details, location, and timestamp.

Field Details

Allowed eventName Values

• SIGNIN

• SIGNOUT

• NOSHOW

Request Body (Sample)

{

  "bookingId": "BLR-XXXX-XXXX-XOBB",

  "lat": "22.6211559",

  "lang": "88.4324648",

  "time": 1774806186000,

  "eventName": "SIGNIN",

  "uniqueRiderEmail": "rider1@gmail.com",

  "client": "gs2-UAT"

}

Sample Curl

POST 'https://api.moveinsync.com/integration/{client-id}/rentlz/booking/attendance'
or
'https://api.moveinsync.in/integration/{client-id}/rentlz/booking/attendance'

--header 'Authorization: Bearer <your token>'

--header 'Content-Type: application/json'

--body '{

  "bookingId": "BLR-XXXX-XXXX-XO1B",

  "lat": "22.6211559",

  "lang": "88.4324648",

  "time": 1774806186000,

  "eventName": "SIGNIN",

  "uniqueRiderEmail": "rider1@gmail.com",

  "client": "gs2-UAT"

}'

? End-to-End API Chronology (Booking Lifecycle Flow)

This section defines the sequence in which APIs should be called during the lifecycle of a booking, from vendor acceptance to trip completion.

? Step 1: Vendor Acceptance

API

POST 
https://api.moveinsync.com/integration/{client-id}/rentlz/booking/status
or
https://api.moveinsync.in/integration/{client-id}/rentlz/booking/status

Description
This API is used by the vendor to accept the booking.

? Step 2: Cab & Driver Allocation

API

POST 
https://api.moveinsync.com/integration/{Client-id}/rentlz/booking/assign/cab-driver
or
https://api.moveinsync.in/integration/{Client-id}/rentlz/booking/assign/cab-driver

Description
This API is used to assign the cab and driver details to the booking.

? Step 3: OTP Submission (Trip Verification Setup)

API

POST 
https://api.moveinsync.com/integration/{client-id}/rentlz/booking/v2/otp 
or
https://api.moveinsync.in/integration/{client-id}/rentlz/booking/v2/otp 

Description
This API is used to submit OTPs for trip start (Sign-In) and trip end (Sign-Out) verification.

? Step 4: Duty Start & Trip Start

API

POST https://api.moveinsync.com/integration/{client-id}/rentlz/booking/start-end
or
https://api.moveinsync.in/integration/{client-id}/rentlz/booking/start-end

Event Sequence

startDuty

startTrip

Description
This API is used to mark:

• Driver duty start

• Trip start

? Step 5: Attendance Events (During Trip)

API

POST https://api.moveinsync.com/integration/{client-id}/rentlz/booking/attendance
or
https://api.moveinsync.in/integration/{client-id}/rentlz/booking/attendance

Event Types

SIGNIN

SIGNOUT

NOSHOW

Description
This API captures employee attendance events during the trip lifecycle.

? Step 6: Trip End & Duty End

API

POST https://api.moveinsync.com/integration/{client-id}/rentlz/booking/start-end
or
https://api.moveinsync.com/integration/{client-id}/rentlz/booking/start-end

Event Sequence

endTrip

endDuty

Description
This API is used to mark:

• Trip completion

• Driver duty end

Flow Summary (Quick View)

1. Vendor Acceptance

2. Cab & Driver Allocation

3. OTP Submission

4. startDuty → startTrip

5. SIGNIN / SIGNOUT / NOSHOW

6. endTrip → endDuty