Four endpoints and a webhook.

Every published listing

The full set of published properties for the key’s organisation, served from publish snapshots. A property that has never been published does not appear, and content being edited right now does not leak.

{
  "listings": [
    {
      "id": "prop_…",
      "slug": "jordaan-1a",
      "nickname": "JOR-1A",
      "active": true,
      "isListed": true,
      "propertyType": "apartment",
      "roomType": "entire_home",
      "address": {
        "street": "…", "postalCode": "1015 AA",
        "city": "Amsterdam", "country": "NL",
        "area": "Jordaan", "latitude": 52.37, "longitude": 4.88
      },
      "accommodates": 2, "bedrooms": 1, "beds": 1,
      "bathrooms": 1, "squareMeter": 58,
      "timezone": "Europe/Amsterdam",
      "pricing": {
        "currency": "EUR",
        "monthlyRateCents": 240000,
        "depositCents": 240000,
        "utilitiesCents": 15000,
        "furnitureCents": null
      },
      "terms": { "minNights": 30, "maxNights": 365 },
      "amenities": ["wifi", "washer", "…"],
      "description": { "title": "…", "summary": "…" },
      "images": [
        {
          "id": "img_…", "isPrimary": true, "caption": null,
          "sortOrder": 0, "width": 2400, "height": 1600, "bytes": 481221,
          "thumbnail": "https://…", "regular": "https://…",
          "large": "https://…", "original": "https://…"
        }
      ],
      "publishedAt": "2026-07-28T09:12:44.000Z"
    }
  ]
}

• Sorted by nickname, so the order is stable between calls.
• If you mirror this into your own database, treat the response as the COMPLETE set and delete rows it no longer contains. That is how an unpublished listing disappears from your site.
• Image URLs are absolute. On local-disk storage they are made absolute against the request origin; on S3 they already are.

One listing

The same object as above, for a single property. 404 if the id is unknown to your organisation or has never been published.

{ "listing": { … same shape as above … } }

Live availability

Per-day availability, computed on request from reservations and calendar blocks. This is the one endpoint that is NOT snapshot-bound: a booking taken thirty seconds ago is reflected here immediately, because a stale calendar double-books a nine-month tenancy.

{
  "days": [
    { "date": "2026-08-03", "status": "booked",      "minNights": 30, "isBaseMinNights": true },
    { "date": "2026-08-04", "status": "reserved",    "minNights": 30, "isBaseMinNights": true },
    { "date": "2026-08-05", "status": "unavailable", "minNights": 30, "isBaseMinNights": true },
    { "date": "2026-08-06", "status": "available",   "minNights": 30, "isBaseMinNights": true }
  ]
}

• `booked` is a confirmed tenancy or later; `reserved` is held but not firm; `unavailable` is a calendar block (renovation, owner use); `available` is bookable.
• Enquiries never block a day. Cancelling releases the days immediately.
• Check-out is EXCLUSIVE. A tenancy ending on the 30th leaves the 30th available, because the handover is at noon that day.
• The listing must be published. An unpublished property returns 404 here too.

Your booking form lands here

Turns a website enquiry into a row staff convert to a reservation in one click, resolved to a guest record, rather than into an email somebody re-types. Anything your form collects beyond the fields below travels in `metadata` untyped, so the form can evolve without a contract change.

201 Created

{ "id": "inq_…" }

• `guestCount` is accepted and folded into `adults`. It is deprecated; send the age bands.
• A bad field returns 400 with a message naming the path, so a broken form is debuggable from the response.