Airbnb reference
Airbnb API guide
Resolve a destination, search stays and inspect a listing. Keep dates, guest counts and currency consistent when comparing listings or asking for a stay price.
Quickstart
Start with Airbnb
Resolve a destination, search stays and inspect a listing. Keep dates, guest counts and currency consistent when comparing listings or asking for a stay price.
These requests use your API key and can spend credits. Check the current price on the endpoint page; each new page is a separate request. Later examples use illustrative identifiers: replace them with values from your earlier response.
1. Resolve the destination
Save the returned location identifier and use it as place_id for search. Similar place names can resolve to different destinations. Parameters and current cost →
curl "https://www.monocrawl.com/v1/airbnb/locations?query=Edinburgh" \ -H "x-api-key: mn_your_key_here"
2. Find stays
For a dated comparison, supply your future checkin and checkout plus the full party. Continue with cursor; this search does not support numbered pages. Parameters and current cost →
curl "https://www.monocrawl.com/v1/airbnb/search-stays?location=Edinburgh&adults=2&limit=10" \ -H "x-api-key: mn_your_key_here"
3. Inspect a selected stay
Replace the illustrative id with a returned listing ID. Preserve the same trip parameters for date-dependent information. Parameters and current cost →
curl "https://www.monocrawl.com/v1/airbnb/stay?id=6332745" \ -H "x-api-key: mn_your_key_here"
Filters and coverage
Choose filters with the source behavior in mind
| Control | Behavior and limits |
|---|---|
| Trip consistency | Keep checkin, checkout, party, currency and filters unchanged while following cursor. Endpoint reference → |
| Availability | Read the declared calendar window; missing dates are not proof that every other date is bookable. Endpoint reference → |
Source availability, ordering and field coverage can change. Inspect warnings and partial-result metadata alongside the rows. See runnable workflows, metric semantics, computed fields and the pagination matrix.
Choose an endpoint
Match the operation to your task
| Your task | Endpoint | When to use it |
|---|---|---|
| Price for a trip | stay-price | Supply the listing, future dates and party; inspect nightly and total price labels and fees. This is not a booking quote guarantee. |
| Available dates | stay-availability | Use the declared month/year controls. A returned availability snapshot does not reserve a stay. |
| Rating summary | stay-rating | A rating summary is not a page of written reviews. Check the catalogue before assuming a separate review operation is available. |
Explore all documented operations by purpose below. Each endpoint reference contains its accepted parameters and current price.
Other operations
Search and discovery
Reviews and offers
Operations
Airbnb
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Airbnb
7 operationsElsewhere
The same registry, other shapes
- Airbnb overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=airbnb— the same rows to your code at runtime, for 0 credits.