Airbnb Availability calendar API
API health
- 24h health
- Normal
- 24h average time
- —
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Check day-by-day availability for an Airbnb listing, including whether each date works for check-in or check-out, minimum and maximum nights, and price. Without dates, the window runs from today for 30 days; reading the calendar never holds or books a stay.
Price $1.39 per 1,000 requests ($0.001389 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
AI prompt
Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.
Please help me write a data collection script with the EveryInfra Airbnb Availability calendar endpoint (airbnb/calendar).
Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to airbnb and action to calendar, and put the parameters inside params.
- Required parameters:
- url: Identifies the target resource based on the action: pass a /rooms/<property_id> URL or property ID for property_detail, reviews, or calendar, or a /users/show/<host_id> URL or host ID for host.
- Optional parameters:
- check_in: Sets a compatibility YYYY-MM-DD start date for the calendar action. If start_date is also supplied, start_date takes precedence; providing since overrides both. Querying calendar dates does not initiate a booking.
- check_out: Sets a compatibility YYYY-MM-DD end date for the calendar action. If end_date is also supplied, end_date takes precedence; providing until overrides both. Querying calendar dates does not hold property availability.
- end_date: Sets the YYYY-MM-DD end date for calendar availability queries. If omitted, the request falls back to check_out or 30 days from the query date (not start_date plus 30 days). Providing until overrides this parameter.
- since: Sets a YYYY-MM-DD start date with action-dependent scope: for reviews, it sets the starting review date; for calendar, it sets the date window start and overrides start_date and check_in.
- start_date: Sets the YYYY-MM-DD start date for calendar availability queries. If omitted, the request falls back to check_in or the current date. Providing since overrides this parameter.
- until: Sets the YYYY-MM-DD end date for the calendar action and overrides end_date and check_out. This parameter controls calendar date windows and does not filter review publication dates.
- limit: The most rows to return in this call, an integer of 1 or more. The default applies when you leave it out, and a call can return fewer rows.
- Returns a list of records. Main fields of each record: id, date, available, available_for_checkin, available_for_checkout, bookable, min_nights, max_nights, price, currency.
- Example request body:
{
"platform": "airbnb",
"action": "calendar",
"params": {
"url": "https://www.airbnb.com/rooms/12937"
}
}
- Price: $1.39 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | airbnb | Platform identifier, fixed value. |
action | body | string | Yes | calendar | Capability identifier, fixed value. |
url | body.params | Not declared | Yes | - | Identifies the target resource based on the action: pass a /rooms/<property_id> URL or property ID for property_detail, reviews, or calendar, or a /users/show/<host_id> URL or host ID for host. Property and host identifiers are not interchangeable. |
check_in | body.params | Not declared | No | - | Sets a compatibility YYYY-MM-DD start date for the calendar action. If start_date is also supplied, start_date takes precedence; providing since overrides both. Querying calendar dates does not initiate a booking. |
check_out | body.params | Not declared | No | - | Sets a compatibility YYYY-MM-DD end date for the calendar action. If end_date is also supplied, end_date takes precedence; providing until overrides both. Querying calendar dates does not hold property availability. |
end_date | body.params | Not declared | No | - | Sets the YYYY-MM-DD end date for calendar availability queries. If omitted, the request falls back to check_out or 30 days from the query date (not start_date plus 30 days). Providing until overrides this parameter. |
since | body.params | Not declared | No | - | Sets a YYYY-MM-DD start date with action-dependent scope: for reviews, it sets the starting review date; for calendar, it sets the date window start and overrides start_date and check_in. |
start_date | body.params | Not declared | No | - | Sets the YYYY-MM-DD start date for calendar availability queries. If omitted, the request falls back to check_in or the current date. Providing since overrides this parameter. |
until | body.params | Not declared | No | - | Sets the YYYY-MM-DD end date for the calendar action and overrides end_date and check_out. This parameter controls calendar date windows and does not filter review publication dates. |
limit | body.params | integer (1–) | No | - | The most rows to return in this call, an integer of 1 or more. The default applies when you leave it out, and a call can return fewer rows. |
Code samples
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "airbnb",
"action": "calendar",
"params": {
"url": "https://www.airbnb.com/rooms/12937"
}
}'[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
Captured September 26, 2026 at 08:56 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2. id, billing and quota differ on every call, so only their shape is shown.
{
"id": "req_…",
"platform": "airbnb",
"action": "calendar",
"results": [
{
"id": "12937",
"date": "2026-09-26",
"available": false,
"available_for_checkin": false,
"available_for_checkout": false,
"bookable": false,
"min_nights": 3,
"max_nights": 1125,
"platform": "airbnb"
},
{
"id": "12937",
"date": "2026-09-27",
"available": false,
"available_for_checkin": false,
"available_for_checkout": false,
"bookable": false,
"min_nights": 3,
"max_nights": 1125,
"platform": "airbnb"
}
],
"count": 31,
"billing": {
"charged": …,
"charged_usd": …,
"balance_after_usd": …,
…
},
"quota": { … }
}Response fields
Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
date | Keeps the platform's own meaning |
available | Keeps the platform's own meaning |
available_for_checkin | Keeps the platform's own meaning |
available_for_checkout | Keeps the platform's own meaning |
bookable | Keeps the platform's own meaning |
min_nights | Keeps the platform's own meaning |
max_nights | Keeps the platform's own meaning |
price | Price as a number without a currency symbol; see currency. |
currency | Currency code of the price (for example CNY, USD). If price is present but currency is null, do not assume a currency. |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
Errors and billing
- 401
- Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
- 422
- Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
- 402
- Insufficient balance. Top up first.
- 429
- The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
- 503
- Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
- 200 empty
- The request completed without data and is not charged (billing.reason = empty_result_refunded).