The resume_link is set following a book request, if the returned itinerary has that link. It can be used to make a retrieve request. The retrieve_link is set following a book request, if the returned itinerary has that link. It can be used to make a booking request. The book_link is set following a price-check request, if the returned property has that link. It can be used to make a deposit-policies request. The deposit_policies_link is set following an availability, cross-sell, or recommendation request, if the returned property has that link. It can be used to make a payment-options request. The payment_options_link is set following an availability, cross-sell, or recommendation request, if the returned property has that link. It can be used to make a price-check request. The price_check_link is set following an availability, cross-sell or recommendation request, if the returned property has that link. The affiliate_reference_id is used in a create booking request and can be used to retrieve subsequent bookings. It will always be 30 days from the time you make a request. The arrival time is autogenerated for cross-sell requests. It will always be 32 days from the day you make a request. The checkout date is autogenerated for availability requests. It will always be 30 days from the day you make a request. The checkin date is autogenerated for availability requests.
Api postman collection code#
This authorization code is generated from your api_key and shared_secret and used as a request header.
Please be aware that the following parameters are autogenerated and will be set in your environment: *Please note that the variables marked as not required with an asterix* are only required for and not What payment_terms should be used when being paid for a resulting booking. What Point of Sale to be used for shop and book. The terms of how a resulting booking should be billed. Whether the itinerary will be created in a held state. The number of people per room to request, format is numberOfAdults]- "2-9,3" would represent two adults, a 9-year-old and a email used in booking requests. The localised language to request, a subset of the BCP47 format. The IATA airport metro code to request in geography related calls. The IATA airport code to request in geography related calls. The region to request in geography related calls. The LCM/expedia property_id to request in content and availability calls. Which host to target, you may wish to override it with " " The following parameters can be defined, only two of which are required: You will need to setup some environment variables before you can use the collections, see here for more information on how Postman handles variables.
The variables and code must remain the same to ensure requests work as expected. Testing notesĭo not edit or change the “ Edit Collection” section. You will also need to ensure that the api_key and shared_secret variables have been set. Import the collections into Postman once you have downloaded them from below.
The collections have been written to be as self-contained as possible, they encapsulate authentication logic and the checkin/checkout self-update with each request.Įach collection also has some basic tests, which can be used in conjunction with the Postman collection runner feature. Requests are grouped in relation to the Swagger material on the site. The Postman collections contain requests for Rapid. Rapid Postman collections Get access to Postman collections for Rapid API versions below Rapid Postman collections
0 kommentar(er)
