Title
Create new category
Edit page index title
Edit category
Edit link
Pricing and Availability
Last-Minute Availability Check
Use the GET /suppliers/{supplier_id}/products/{product_id}/availability endpoint for a last-minute check, especially for products with low inventory (rate_id should be used in this kind of request). This helps avoid hold or booking failures.
Last-Minute Pricing Check
Use GET /suppliers/{supplier_id}/products/{product_id}/pricing/schedule for a last-minute pricing check. This can be set as a configurable option based on transaction volume. Your Travel Curious Implementation manager can tell you if a particular supplier changes pricing frequently. This will avoid a hold or booking failure later.
Price Schedule vs. Rates
Get Price Schedule needs to be implemented in conjunction with the Get Rates call, one does not replace the other, you must support both to get all the details needed.
Implement Price Schedule with the ability to identify and properly use the pricing types: net, retail, original. net and retail should be considered at a minimum and should be used appropriately and according to your contracts with your operators. If your system does not support the use of both retail and net, please let your integration manager know that Travel Curious can set up pricing rules to provide the type of rates that you need per operator.
Ensure price amounts (original, net, retails) and priceId used are always the ones from the price schedule response
Travel Curious added a header to the GET Rates / GET Rate Reseller API request to allow the Resellers to opt into a new treatment of missing dollar amount information on Rate Prices, by adding a request header to their requests
If you call with the
X-Allow-Nil-Static-Prices=trueheader: those prices that were not provided by the Supplier will havenilvalues explicitly. If you see product rates with $0.00 amount on any or all of Net, Retail and Original fields, it will be clear that the Supplier submitted the data intentionally that way.- In case the Supplier updates the price data and instead of
nillthey set an amount, it won’t create new rate ids, just price ids, which is the same behavior if the supplier updates their prices. The same could happen the other way around
- In case the Supplier updates the price data and instead of
If the you call without the header: the new treatment of missing dollar amount information on Rate Prices won’t be applicable and you will continue to see it as $0.00 amount and won’t be able to discern the difference between a missing price vs a true $0.00 price.
Note that the same behavior is applied to Price Schedule endpoint and the embedded rates under booking items in Booking endpoint responses.
Questions? We'd love to hear them. Contact Travel Curious Support.