Accommodation availability provides availability and pricing information for stays.
All endpoints are scoped to the organization that owns the API key:
/store/v0
Get accommodation availability feed
GET /store/v0/accommodations/availabilitiesQuery parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
start_date | string | Yes | Check-in date (YYYY-MM-DD) |
end_date | string | Yes | Check-out date (YYYY-MM-DD) |
accommodation_ids[] | string[] | No | Filter to a set of accommodation public IDs |
occupancy[adults] | integer | No | Default depends on server-side occupancy normalization |
occupancy[children] | integer | No | Defaults to 0 if omitted |
occupancy[infants] | integer | No | Defaults to 0 if omitted |
Example request
GET /store/v0/accommodations/availabilities?start_date=2026-03-20&end_date=2026-03-23&accommodation_ids[]=2f1b2d7c-6a51-4d35-9b5a-9b0c3b8efb2a&accommodation_ids[]=3a2b1c0d-9e8f-4a5b-8c7d-6e5f4a3b2c1d&occupancy[adults]=2&occupancy[children]=0&occupancy[infants]=0Response
This endpoint returns a "feed" object from SERVOS. The exact response shape may evolve; treat it as a structured JSON document containing availability/pricing per accommodation for the requested date range and occupancy.
Prices cover the whole stay from start_date to end_date, so they include pricing rules that depend on the stay's length.
If you need a strict schema for this response for your integration, contact the SERVOS team with an example response from your target location.
Errors
- Invalid dates return
400with{ "error": "Invalid date format: ...", "details": {} }
See Errors.
