HTTP 202 Responses

If you and the operator support pending booking functionality, an HTTP 202 response may be returned during the booking flow. Tickets will not be returned with a 202 response, instead, you must regularly fetch the booking ID from the GET Booking API endpoint to retrieve the confirmed tickets when the booking transitions from PENDING status to OPEN. This is recommended for those Resellers partners like you who want to connect to high volume systems or live event systems. These are the systems typically using 202 Pending booking responses.

• Travel Curious will send an HTTP 202 response with Booking status PENDING to the Reseller
• Reseller receives the usual Booking response JSON but without the tickets because it was not provided by the Supplier or Ticketing System yet
• Reseller needs to call Travel Curious's GET Booking API to get the confirmation with the ticket details included in it. This could be within a few minutes or up to 24 hrs prior to the event.
• Once Travel Curious gets the confirmation from the Supplier or Ticketing System, the booking status will change from PENDING to OPEN and the Reseller will be able to see the ticket details returned in the booking response.