Sell packages
Hotels turn some of their special offers into packages for agencies: a Christmas stay, a spa weekend, a long-stay deal. A package comes with everything you need to sell it:
- the hotel's own texts and picture;
- the dates on which it can be booked;
- the stays it is for;
- the rate plan you book it on, net or at a commission.
You do not subscribe to a package. You see it as soon as the hotel shares it
with you, and booking it subscribes you to its rate plan. Each morning we
e-mail your account the packages shared with you since the day before. To
pick up changes between those mails, call GET /packages with
updated_since.
The flow is three calls:
GET /packageslists what you can sell.POST /searchwithpackageprices one for your guests.POST /bookingwithpackagebooks it.
1. GET /packages
GET /api/b2b/v1/packages?locale=en
Authorization: Bearer <your token>
| Parameter | Required | |
|---|---|---|
locale |
yes | Language of the texts: en, bg, el, de, ro, ru, pl |
properties |
no | Comma-separated property ids |
updated_since |
no | Only packages shared or changed since then, e.g. 2026-11-18T10:00:00+02:00 or 2026-11-18 |
The answer is a list of packages (an answer from our test environment, with the hotel's own texts replaced):
[
{
"id": 4,
"property_id": 189,
"title": "ROMANTIC PACKAGE",
"subtitle": "",
"text": "<p>Two nights for two in a double room with a river view, a romantic dinner and the spa.</p>",
"image": { "url": "https://staging.quendoo.com/files/mf/5c0e…_romantic.webp", "width": 840, "height": 596 },
"bookable": { "from": "2026-01-01", "to": "2026-12-31" },
"stay": { "check_in_from": "2026-01-01", "check_in_to": "2026-12-31", "min_nights": 2, "max_nights": 2 },
"rate_plans": [ { "id": 11177, "type": "net" } ],
"first_stay": { "check_in": "2026-11-18", "check_out": "2026-11-20", "nights": 2, "occupancy": [ { "adults": 2, "children": [] } ] },
"stays_checked_at": "2026-11-18T07:43:36Z",
"updated_at": "2026-11-18T09:42:59+02:00"
}
]
| Field | Meaning |
|---|---|
id |
The package. Send it as package to /search and /booking |
property_id |
The hotel. GET /properties has its details |
title, subtitle, text |
The hotel's texts; text is HTML |
image |
The offer's picture, or null |
bookable |
The dates on which the package can be booked. null means no limit on that side |
stay |
The stays it is for: the check-in window and the nights. null means no limit |
rate_plans |
The rate plans you book it on: net, or commission with commission_percent |
first_stay |
The first free stay: dates only, or null until it has been worked out |
stays_checked_at |
When first_stay was worked out (UTC) |
updated_at |
When the hotel shared or last changed the package |
There is no price here. A package's price for you depends on the stay,
the guests and your terms, so /search works it out. The first_stay dates
are where to start.
A package leaves the list when:
- the offer ends or is switched off;
- the hotel stops sharing it, or its rate plan, with you;
- the rate plan is hidden from agencies.
Poll with updated_since to pick up new and changed packages. Compare the
full list to drop the ones that went away.
2. POST /search with package
{
"locale": "en",
"package": 4,
"occupancy": [ { "adults": 2, "children": [] } ]
}
- Without dates, the package's first free stay is searched. The answer says which dates were priced.
- With dates (
checkin_date,checkout_date), they must fit the package'sstay. If they do not, error 3 names the rule they miss: This package is for at least 2 nights. properties,locationsandcountry_codesare not allowed. The package names its hotel. Sending one is error 4.
The answer is an ordinary search answer: the same id (your search_id),
expires and properties with their rooms, rates and prices. It carries
three more fields:
{
"package": 4,
"checkin_date": "2026-11-18",
"checkout_date": "2026-11-20",
"id": "k2Vf…(opaque, ~250 characters)",
"expires": 1794990540,
"properties": [
{
"property": { "id": 189, "name": "Riverside Hotel", "…": "…" },
"rooms": [
{
"room": { "id": 451, "name": "Double room with terrace and river view", "…": "…" },
"sell_qty": 1,
"rates": [
{
"rate": { "id": 11177, "name": "ROMANTIC PACKAGE · B2B -10%", "…": "…" },
"prices": [
{ "id": "rMqnkuU8IC6z…(opaque)", "price": 852.3, "discount_percent": 10, "old_price": 947, "…": "…" }
]
}
]
}
]
}
]
}
Here the package's net rate plan is 10 % below the hotel's website price:
947 on the website, 852.30 for you. prices[].id is the
accommodation_id you book with.
Only the package's rate plans are in it, priced for you whether you have
subscribed to them or not. An empty properties list means nothing is free
for that stay and party: try other dates.
3. POST /booking with package
Book exactly as after any search (Search and book), and
add package:
{
"search_id": "k2Vf…",
"property": 189,
"package": 4,
"ref_id": "AG-2026-00417",
"checkin_date": "2026-11-18",
"checkout_date": "2026-11-20",
"client": { "first_name": "Ivan", "last_name": "Petrov", "email": "[email protected]", "phone": "+359888123456" },
"items": [ { "room": 451, "rate": 11177, "accommodation_id": "rMqnkuU8IC6z…(from the search)" } ]
}
package does two things:
- it subscribes you to the package's rate plans if you have not subscribed yet, before the booking is made;
- it tells the hotel the booking came from the package.
Everything else about the booking is unchanged: the sealed price, the checks, the answer, cancellation and webhooks.
Without package, a rate plan you have not subscribed to is refused with
error 8, as it always is. Either send package, or subscribe first with
POST /rate-plans/subscribe.
Errors
| Code | When |
|---|---|
| 1 | locale missing (GET /packages) |
| 2 | locale unknown |
| 3 | A bad date, a stay that does not fit the package, or no free stay known yet when you sent no dates |
| 4 | A field /search does not take with package (properties, locations, country_codes) |
| 8 | package is not a positive number, or is not a package shared with you |
The rest are the ordinary errors of /search and /booking
(Errors and good practice).