Overview
The Bulk Inventories API allows you to fetch inventory availability for multiple properties in a single request. This is more efficient than calling the single-property inventory endpoint multiple times when you need to check availability across several properties.Fetching Bulk Inventories
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
| fromDate | string (YYYY-MM-DD) | Yes | Start date for the inventory query |
| toDate | string (YYYY-MM-DD) | Yes | End date for the inventory query |
| propertyIds | array of strings | Yes | List of property IDs to fetch inventories for |
Example Request
Example Response
Response Fields
| Field | Type | Description |
|---|---|---|
| propertyId | string | Identifier of the property |
| inventories | array | List of daily inventory details |
| inventories[].date | string (date) | Date for the inventory entry |
| inventories[].quantity | integer | Number of units available |
| inventories[].stopSell | boolean | If true, property is not available for sale on this date |
| inventories[].minimumStay | integer | Minimum nights required |
| inventories[].maximumStay | integer | Maximum nights allowed |
When to Use Bulk vs Single Fetch
| Scenario | Recommended Endpoint |
|---|---|
| Check availability for a single property | GET /v1/properties/{propertyId}/inventories |
| Check availability across multiple properties | POST /v1/inventories |
| Get availability for all properties | GET /v1/properties/inventories |
Authentication
All requests must include the following headers:Api-Key: Your API key for authenticationChannel-Id: Identifier for the channel making the request
Error Handling
The API returns standard HTTP status codes:- 200: Success
- 400: Bad Request - missing or invalid fields
- 401: Unauthorized
- 500: Internal Server Error

