To assist you in testing your integration's handling of possible booking error states, test requests are available for all methods of the Rapid Booking API.
To send a test request for a Rapid Booking API method, include an additional HTTP header named test in your booking request and use the appropriate value from the tables below.
Please review our testing notes in full before attempting any tests. A list of test header values and their responses can be found below.
Note: Failing to send test header, or sending an invalid test header, will cause the booking to be processed live.
- Always check the returned cancellation policy to ensure no penalties will apply.
- Cancelling an on-hold test booking (
hold = true) without confirming it will cause the itinerary ID returned by the initial response to be reused by our booking system, since the original itinerary was never completed. Be aware of potential false duplicates in this testing scenario. - Test bookings are not surfaced to our booking support agents' platform. Contact your Rapid representative or partner support for test booking issues.
- Please note that when in a test environment some test responses are stubbed. Therefore responses will not always match the content expected in response.
- Before launch, during testing, please ensure you send your queries to test.ean.com. This endpoint never makes a live booking, but creates a mock booking in a test environment. This can still be used post-launch for testing production credentials.
- The test header will result in a static 'canned' message returned as a response. Therefore, rates/content etc. returned may not be relevant with the properties being tested.
Live tests are simply standard live bookings made with a real credit card, without a test header that are cancelled after confirmation. It is your responsibility to select acceptable candidate properties and to cancel your own tests. We recommend live tests only for the very final stages of pre-launch development. Rapid is not responsible for any charges incurred by in-policy cancellations or non-refundable rates used for live tests.
- Search for stays at least 60-90 days into the future.
- Select rooms without any cancellation penalties before the policy period (some properties charge for both inside- and outside-policy cancellations).
- Verify the room does not have a false
refundable flag. - Use 'test booking' as your guest name values in the booking request's
rooms object. - Use the actual name, address, and phone number associated with your credit card in the
billing_contact object.
- Rooms must be cancelled within 48 hours of booking.
- Allow 5 business days to process the refund of the cancel fee.
- Allow 30 business days for the credit to be posted to the credit card account.
