Testing

After a successful development, third party should do several tests to conclude that this API connection connection is working as intended.

Bookings creation

First thing to test is bookings creation. Tests are done by creating bookings via the API, and then comparing results with values third party expect. Values to compare are:

• pickup and drop-off office
• pickup and drop-off date and time
• car rental prices (prepaid and pay on arrival part)
• selected additions and additions prices (prepaid and pay on arrival part)
• meet & greet location (if used by a provider)
• drivers list (or dummy list of drivers) for young/old/additional drivers fees
• different credentials (if third party has multiple brands/partners connecting)
• different environments (test and production, or even different providers, in case you are connecting multiple providers)

Bookings modification

Second thing to test is bookings modification. Test is done by opening already saved booking, changing some properties (e.g. pickup date or office, list of drivers, etc.) and then saving the booking.

Bookings cancellation

Third thing to test is bookings cancellation. Test is done by cancelling already saved booking.

How to self-check the results

Booking create, calculate and save methods always have a response of BookingModel type, that represent current state of the booking in provider's database. So third party should read that response and compare the values with values on their side. This is preferred way of checking for developer level.

Another way of checking booking is by using B2B web. One can access B2B web by using same credentials as in this API, and there all the details about saved booking can be found.