close

Sign in

To view secure documentation please login with EAN Service Desk, using the link below.

EAN service desk

No EAN Service Desk account?

Please contact your EAN representative

Login
Sign in
Rapid

Rapid Booking Test RequestsAll Versions

To assist you in testing your integration's handling of possible booking error states, test requests are available for all methods of the Booking API.

To send a test request for a 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.

Create Booking

Test Header Value HTTP Code & Response
STANDARD 201 - Standard response
CC_DECLINED 400 - Credit card declined error
ROOMS_UNAVAILABLE 410 - Rooms unavailable error
PRICE_MISMATCH 409 - Price mismatch error
PRICE_UNAVAILABLE 410 - Price unavailable (sold out) error
INTERNAL_SERVER_ERROR 500 - Internal Error
SERVICE_UNAVAILABLE 503 - Service Unavailable
Important Test Booking Notes
  • Failing to send 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.
    • Always use refundable rates for test bookings.
  • Test bookings will return itinerary IDs within the range 900000000000 - 999999999999
  • 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 EAN representative or partner support for test booking issues.
Important Live Test Booking Notes

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. EAN is not responsible for any charges incurred by in-policy cancellations or nonrefundable rates used for live tests

Placing Live Test Bookings

  • 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 associated with your credit card in the billing_contact object.

Cancelling Live Test Bookings

  • 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

Retrieve Booking


Test Header ValueHTTP Code & Response
STANDARD200 - Standard response
INTERNAL_SERVER_ERROR
500 - Internal Error
SERVICE_UNAVAILABLE503 - Service Unavailable

Cancel Booking

Test Header ValueHTTP Code & Response
STANDARD204 - No Content - standard response
POST_STAY_CANCEL400 - Invalid response from upstream server error
INTERNAL_SERVER_ERROR500 - Internal Error
SERVICE_UNAVAILABLE503 - Service Unavailable 
New Release - EAN Rapid 2.1

EAN Rapid 2.1 has been fully released to production! Find out what's new or see our changelog details to get started. Rapid 2.0 documentation is still available via the version drop-down menu in the upper right corner of each doc page.