How to Onboard a New External Vendor

Created by Moveinsync Help, Modified on Mon, 18 May at 3:32 AM by Moveinsync Help

Below are the steps for integrating an external vendor with MIS and Rentlz systems:

1. API Integration

We will share our API documentation with the vendor, which includes all required endpoints.
This can be the first step when initiating discussions with the vendor.

Booking Management API:Doc
https://helpcenter.moveinsync.com/support/solutions/articles/1070000134486-rentlz-booking-management-api

This doc can be different for different customer please consult with Rentlz POD before sending the API doc

Based on our shared documentation, the vendor will develop their APIs for:

Create Booking
Cancel Booking
Update Booking

They will then share their API details with us for integration

Sample API Endpoints (for Vendor ID – XXXXX):

CREATE - POST https://api-xxxxx.xxxxx.com/gBydrMaFrZteHQEvk/moveinsync/bookings
UPDATE - PUT https://api-xxxxx.xxxxx.com/gBydrMaFrZteHQEvk/moveinsync/bookings/MISBookingId
CANCEL - DELETE https://api-xxxxx.xxxxx.com/gBydrMaFrZteHQEvk/moveinsync/bookings/cancel
Billing Management API (if applicable): Doc - do not send with out consulting with rentlz POD as this has some custom flows
ihttps://helpcenter.moveinsync.com/support/solutions/articles/1070000134492-rentlz-billing-management-api

2. Vendor & Vehicle Setup (MIS System Configuration)

To be completed by the Implementation Manager or TAM for that account.

Step	Task	Required Details
1	Create Vendor Profile (Manage Vendor Page)	Vendor ID, Name, Point of Contact, Email, Phone
2	Create Vehicle Type	Vehicle Type Name, Capacity, Fuel Type (only required if billing needs to be done)
3	Create Contract for Vendor	Rate card (from customer) (only required if billing needs to be done)
4	Create Virtual Cab Profile	Vendor, Vehicle Type, Registration No., Garage Name & Geocode, Vehicle ID
5	Share Master Data with Vendor	Share Booking Type, City, and Cab Type list with the vendor so they can configure the same at their end.
6	Create vendor manager profile	Create a vendor manager profile and share the creds with the vendor to access MIS for testing and future uses.

3. Configuration and Access

Once the vendor shares their API details, raise a TO (Task Order) with these API endpoints and assign it to the Rentlz developer for backend configuration.
Sample TO: TO-19141
Raise another TO for the External Vendor Server Team (Deepanshu or team) to generate a username and password. - once create send it to the vendor
Sample TO: TO-21280
Our endpoints and base URL should already be in the shared document.

4. Final Step

PMS: There are 2 folders where configuration needs to be added — Create a SE ticket for this (reference SE: https://moveinsync.atlassian.net/browse/SE-57347 )

externalServiceVendor: In this folder, the vendor GUID and vendor ID need to be configured.
extVendorClientMapping: In this folder, the vendor GUID and vendor username (provided by Deepanshu) need to be configured.
Example: "VENinfos-ysIN-DTRV-L$00-000000000342": "infosys-INDTRVL-ITHN-Che"

How to Onboard a New External Vendor

1. API Integration

2. Vendor & Vehicle Setup (MIS System Configuration)

3. Configuration and Access

4. Final StepPMS: There are 2 folders where configuration needs to be added — Create a SE ticket for this (reference SE: https://moveinsync.atlassian.net/browse/SE-57347 )

externalServiceVendor: In this folder, the vendor GUID and vendor ID need to be configured.

extVendorClientMapping: In this folder, the vendor GUID and vendor username (provided by Deepanshu) need to be configured. Example: "VENinfos-ysIN-DTRV-L$00-000000000342": "infosys-INDTRVL-ITHN-Che"

4. Final Step

PMS: There are 2 folders where configuration needs to be added — Create a SE ticket for this (reference SE: https://moveinsync.atlassian.net/browse/SE-57347 )

extVendorClientMapping: In this folder, the vendor GUID and vendor username (provided by Deepanshu) need to be configured.
Example: "VENinfos-ysIN-DTRV-L$00-000000000342": "infosys-INDTRVL-ITHN-Che"