The Kabora partner API

Kabora exposes a small read-and-write API so tools you already use — dynamic pricing especially — can read your listings and calendar and push rates back.

Create a key under Settings → API access. Each key belongs to one account, carries only the scopes you grant it, and can be revoked without affecting anything else. Send it on every request:

• Authorization: Bearer <key>

Listings

GET /api/partner/v1/properties

Every listing with its location, capacity, amenities and base rate — enough for a pricing tool to map its own records onto yours.

Money

Every amount is a whole number of hundredths of the listing's own currency, which each listing carries as currency — whatever that currency does with decimals. A $150.00 night is 15000 beside USD, and a ¥15,000 night is 1500000 beside JPY, although the yen has no smaller coin. The fields end in _cents for every currency, and price_cents in a push is read the same way. The public feed, which needs no key, gives the same prices in whole units instead.

Calendar

GET /api/partner/v1/properties/:id/calendar?start=&end=

Night by night: price, minimum stay, availability.

POST /api/partner/v1/properties/:id/calendar

Push rates back, as { days: [{ date, price_cents, min_nights, available }] }.

A night you priced by hand is never overwritten. Those dates come back in skipped_host_priced_dates so the tool can show you what it did not touch, rather than quietly disagreeing with a decision you made on purpose. If you set a wedding weekend to four hundred, it stays four hundred.

Reservations

GET /api/partner/v1/reservations?since=

Stays with their full financial breakdown, 500 at a time (has_more says when there are more); since returns stays checking out on or after that date.

Guest data is limited to a first name. A pricing tool needs to know a stay happened and what it earned; it has no business knowing who slept there.