Release notes

2026-11-03: Every offer of a property in a bulk search with "all"

max_offers_per_property in POST /properties/availability now also takes the string "all", which lists every offer of each property, cheapest first, with no count. Send 1 for the cheapest offer, 10 for the ten cheapest, or "all" for every offer; a number lists the same offers as "all" wherever the property has no more than that many, so both forms stay consistent. A number from 1 to 250 works as before. A string other than "all" now answers 400 INVALID_REQUEST with field set to max_offers_per_property, where a number written as text such as "5" was refused without a field before. See Offers per property

2026-11-03: Every code a projection issue carries, and a lifted stay limit reads as null

A projection_issues entry now lists every code the service sends in it. Besides INTERNAL_ERROR, a tax issue carries UNSUPPORTED_FX_PAIR when a fixed tax amount is kept in a currency with no current rate to your currency_code, with retryable false, and SUBSTRATE_DATA_INVARIANT when the property's stored tax data is inconsistent. Both were already sent and are now part of the contract, so a client that checks code against the published list accepts them. In POST /availability/check, a stay bound in nights_resolved (min_stay_through, max_stay_through, min_stay_arrival, max_stay_arrival) that a rule lifts is now null instead of 0, so every bound is a number of nights from 1 up or null for no limit, as the contract always stated. The verdict does not change. See Errors and Currencies, occupancy and allocations

2026-11-03: The currencies a search can be priced in

GET /reference/currencies lists, by ISO 4217 code, every currency the service holds a current exchange rate for, so you can choose currency_code before you search. A hotel that keeps its prices in another currency cannot price a code outside the list: the single-property search answers 422 UNSUPPORTED_FX_PAIR and the bulk search gives that hotel's row the same error_code, as before. The list carries an ETag and answers 304 to a matching If-None-Match. AI agents reach it as the list_currencies tool. No existing field changes. See Currency

2026-11-01: Every booking you make is invoiced to your account

You collect from your guests and settle with the seller on account, so every stay, tour, transfer, flight and package you book is now invoiced to your account under your payment terms and confirmed, a rate the seller's own guests pay at the property included. Before, such a rate was booked as paid by the guest at the hotel. An account that does not settle on account with the seller can no longer book any rate: prebook and /book answer 422 PAYMENT_INTENT_NOT_SUPPORTED. payment_intent_kind on the book requests now accepts only INVOICE; PAY_AT_PROPERTY returns 422 PAYMENT_INTENT_NOT_SUPPORTED with field set to payment_intent_kind. Omitting the field, the normal case, needs no change. policy_card.payment_intent_kind in search keeps saying how the seller's own guests pay. See How the stay is settled

2026-10-20: The price before promotion carries its own tax

grand_total_before_promotion now adds the exclusive tax the rooms' prices before promotion owe, each room's rounded on its own, instead of the tax of the discounted price, so it is the price the guest would pay with no promotion. A room of 4776.64 TRY that lists at 5970.80 TRY before a promotion, under a 1 percent accommodation tax on the price less 10 percent VAT, now publishes 6025.08 TRY where it published 6014.22. Only promoted offers under a tax added at booking move; grand_total, stay_total, stay_total_before_promotion, the promotion lines and every booking amount do not change. See Taxes in the payable total

2026-10-19: A promotion lowers the price a markup is computed on

On a net rate property, a percentage markup on your rates is now computed on the night after its promotions, so a promotion takes its own share off the price you are quoted. A 40000 TRY night with a 30% promotion and a 3% markup is now quoted at 28840.00, with stay_total_before_promotion at 41200.00 and a promotion_lines[].amount of -12360.00. Before, the same night was quoted at 29200.00 with a line of -12000.00, 29% off. Offer search, POST /availability/check, prebook and book follow the same rule. Fixed markups and stays without a promotion do not change, and no field is added or removed. See Breakdowns add up

2026-10-18: Prices follow the party's adult count and the stay's length

Offer search, POST /availability/check, prebook and book now price a stay from the stored price of the party's adult count at the stay's own length. A property that stores a price for stays of seven nights or more shows that price on each night of a seven night stay, in nights[], per_night_avg and stay_total, and the nightly price on each night of a six night stay. A count without a stored price takes the next higher stored count, and adults above the highest stored count pay the property's extra adult fee, which extra_guest_amount shows. A party the property cannot price answers REJECT at gate 11 on the check, whose detail names the missing price, the next higher count, the extra adult fee or the stay length, and is left out of offer search. extra_guest_amount now holds the extra adult fee and child prices only; the price of the adult count is not part of it. No field is added or removed. See Prices by occupancy and stay length

2026-10-18: A child's age without a price names its reason

unavailable_reason gains GUEST_AGE_NOT_PRICED. A property answers it on bulk and place search results and on the detail response when the party fits a room but a requested child's age has no price there for its position, the adult count and the stay dates. No other room split or room count of the same party changes it, so searching again with more rooms does not help. Treat a value you do not know as unavailable. See Why a property returns no allocation

2026-10-18: Place search facet options lead with the busiest

Each facets group of a place search now lists its options with the most properties first, then by label in the request language, then by value. Before, they came in value order, so a group could open with options at 0 ahead of those with properties. stars still runs from 5 down to 0 and guest_scores from 9 down to 6. Counts and fields do not change. See Search a whole place

2026-10-18: Each room is rounded on its own

A multi-room allocation now rounds each room's price and each of its tax totals on its own, and its totals are the sums of its rooms. The same rooms therefore quote the same total as one allocation and as a selection_tokens basket of single-room selections, the way the major online travel agencies state a multi-room booking. Before, the allocation was rounded once and its rooms were settled against that figure, so two rooms with 3.6364 and 6.5454 EUR exclusive tax showed 3.64 and 6.54 under a grand_total of 570.18 while the same two rooms as a basket charged 570.19. The allocation now shows 3.64 and 6.55 and a grand_total of 570.19

A multi-room grand_total, grand_total_before_promotion and the prebook and booking tax totals can move by at most one minor unit for every two rooms. Single-room allocations and response fields do not change. See Breakdowns add up

2026-10-17: A booking states its tax

GET /bookings/{public_id}, the /book and cancellation responses and the booking webhooks now carry tax_total_exclusive, the part of stay_total that is tax collected with the booking, and tax_total_payable_at_property, the tax and fees the guest pays the property outside stay_total. Both are the amounts prebook stated, at the currency's minor unit, and 0.00 when none applies. Before, a booking stated only its total, so the split had to be kept from the prebook response. No existing field changes. See Taxes in the payable total.

2026-10-17: A multi-room allocation's tax adds up

The tax of an allocation is now rounded once for each inclusion mode and published as the breakdown of that figure: the slots' tax totals add up to the allocation's tax, and each slot's tax lines add up to that slot's totals. Before, each figure was rounded on its own, so two rooms with 3.6364 and 6.5454 EUR exclusive tax showed 3.64 and 6.55 while grand_total held 10.18; they now show 3.64 and 6.54. No payable total changes, and response fields are unchanged. See Taxes in the payable total.

2026-10-17: Places are addressed by the Adrasis place id

Every place is now addressed by its Adrasis place id, the place's entry in the Adrasis place dictionary as a decimal string such as "87066", the same in every environment, and every country by its ISO 3166-1 alpha-2 code such as "TR" (Property content). The fields that carry them are named for it. A request that still sends an old name answers 400 INVALID_REQUEST naming that field, and an error's field names the new field.

2026-10-16: Basket tax totals follow the amounts collected

An accommodation basket's tax_total_exclusive now sums each selected unit's tax after rounding to the booking currency, matching the tax included in its payable total. Cancellation uses the same collected amount for each item. Two units with 258.4167 TRY tax each therefore report 516.84 TRY together. Response fields are unchanged. See Taxes in the payable total.

2026-10-15: Percentage taxes can include other charges

A property's percentage tax can apply to its room amount plus other charges, such as a service fee. Returned tax lines and payable totals account for this configuration, including when charges are already included in the price. Do not reconstruct every tax from the room amount alone. The response fields and inclusion modes are unchanged. See Taxes in the payable total.

2026-10-14: Tax names and charged-night limits

Accommodation tax lines use the property's configured name when present; otherwise label uses a general name in the requested language. Configured names are returned as written. Use the numeric tax fields for classification.

Tax amounts respect the configured limit on charged stay nights and child exemptions. Use the returned tax amount instead of extending a nightly amount over the entire stay. The tax line's fields and inclusion modes are unchanged. See Taxes in the payable total.

2026-10-14: Exclusive tax is included in the payable total

Accommodation grand_total now includes exclusive tax collected with the booking. Prebook exposes that tax as tax_total_exclusive, and the booking's stay_total carries the same payable total. Room and night amounts continue to describe the accommodation price. Tax payable at the property stays separate. Send the published grand_total in quoted; do not add tax again.

Allocation ranking still uses the accommodation amount before exclusive tax. A fixed tax per room can therefore make the winning allocation more expensive after tax than another choice. Cancellation refunds the cancelled stay's exclusive tax, including for a non-refundable rate; penalties remain based on the accommodation amount. See Taxes in the payable total.

2026-10-14: List and change-feed cursors are encrypted

Cursors were always opaque; the property list, booking list and change feed cursors are now encrypted as well, so they carry nothing readable. A cursor issued before this change is refused once: a property list or booking list cursor answers 400 INVALID_REQUEST (the booking list names cursor in field), so start the walk again from the first page; a change-feed cursor answers 409 CATALOG_VERSION_CHANGED, so rebuild the snapshot with a full GET /properties walk and continue from its changes_cursor. That walk also replaces any hotel id stored before the 2026-10-13 change.

2026-10-13: Hotels are addressed by the Adrasis hotel id

Field names do not change; the hotel ids they carry do. Every hotel is now addressed by its Adrasis hotel id, the hotel's entry in the Adrasis catalog as a decimal string such as "72259", the same in every environment and for every seller on Adrasis (Property content).

2026-10-13: Place-search limits

Sorted and filtered place searches, including searches around a point, accept up to 10,000 visible properties and price up to 1,000 after ruling out unavailable properties. Exceeding either limit returns 400 PLACE_TOO_BROAD. Property-level filters can narrow the search; price, board and refundability filters apply after pricing and cannot reduce these counts. Catalogue-order paging remains unchanged. See Search a whole place.

2026-10-11: Tax amounts are backed out of tax-inclusive prices

Requests and responses keep their shape; some tax values change.

Prices, stay_total and grand_total do not change. Bookings made before this change keep the tax they were made with.

2026-10-11: Tours, transfers, flights and packages settle under your payment terms

2026-10-11: The payment intent you send no longer overrides a rate's terms

2026-10-10: Prepaid rates for accounts that settle on account

Existing requests and responses keep their shape.

Pay-at-property and invoice rates are unchanged. See Booking flow.

2026-10-09: Full property room list and custom room selection

Under strict, room lists follow the requested occupancy order. Under flexible, the single list prices the entire party in one room. If only a multi-room stay fits, that list is empty and best_allocation carries the recommendation. Each room product exposes selectable_quantity, the minimum remaining physical quantity across the stay. Products can share inventory.

Repeated unit tokens request additional physical rooms. All selections must share the property, stay and request context. Each room retains its own terms. Mixing pay-at-property and prepaid rooms returns 422 MIXED_SETTLEMENT.

Bulk property and place availability still return one allocation per property. Detail usage counts only the rooms in the best allocation, regardless of room-list length. Book, idempotent replay and whole-booking cancellation keep their existing endpoints.

2026-10-09: Search around a point, property notes and licence number

All three changes add optional request fields or new response fields; existing requests and responses keep their shape.

See Booking flow for near and Property content for the two content fields.

2026-10-07: Stable codes beside offer labels

Offer labels are worded in the requested language. Each now has a stable code beside it, and integrations branch on the code, never on the words:

Where to next

• Detail request and response examples
• Multi-room prebook examples
• Usage measurement