Fetch Airbnb listing search with priced stays, listing details, guest reviews and availability calendars as structured JSON with one SocialCrawl API key. Reads are priced in credits.
4 active endpoints. Search, listing, reviews and availability.
Four read endpoints for public Airbnb data. Search a place for priced listings, read one listing in full, page through guest reviews, and read a listing's availability calendar.
/v1/airbnb/searchUp to 18 listings a page for a place. Each has its name, coordinates, rating out of 5, review count, photos and a priced stay: the total, the per-night price, the total before any discount, and taxes and fees. Without dates it prices Airbnb's default stay and says which dates it used. Standard tier (1 credit).
location, check_in, check_out, adults, children, infants, pets, cursor
/v1/airbnb/listingOne listing in full. Returns the title, property type, description, area, coordinates, rating and review count, photos, amenities and the check-in and check-out times. With dates it also prices that stay. A listing id that does not exist answers 503 with a note to check the id, and is never charged. Standard tier (1 credit).
id, url, check_in, check_out, adults
/v1/airbnb/listing/reviewsA listing's guest reviews, up to 24 a page. Each has its rating out of 5, the text in the language the guest wrote it, date, the guest's first name and location, and the host's reply. data.total is the listing's full review count. Advanced tier (5 credits).
id, url, limit, cursor
/v1/airbnb/listing/availabilityA listing's calendar night by night for up to 12 months. For each night it says whether it is available and bookable, whether a stay can start or end on it, and the minimum and maximum stay. There is no per-night price here; the listing route with dates prices a stay. Advanced tier (5 credits).
id, url, from, months
Returns Airbnb listings for a place with name, coordinates, rating out of 5, review count, photos, and the priced stay: total, per night, before discount, taxes and fees.
Use it to compare stays in an area. Add check_in and check_out to price your dates, or you get Airbnb's default stay.
1 credit
location · A place, for example Lisbon, Portugal.
$ curl https://www.socialcrawl.dev/v1/airbnb/search?location=Lisbon%2C+Portugal \
-H "x-api-key: sc_YOUR_API_KEY"// Running this live needs your own API key. Hit "Try it" to see an example responseAirbnb is a normal SocialCrawl data surface. You call GET /v1/airbnb/… with an API key, spend credits on live misses, and get a single JSON envelope back.
Send your key in the x-api-key header. No Airbnb account or developer app is needed for public reads. The same key works across SocialCrawl platforms.
Search takes location and optional dates and guests. Listing routes accept id or url. Dates are YYYY-MM-DD. Formats are validated before any charge.
Search and listing detail cost 1 credit. Guest reviews and availability cost 5 credits. Cache hits cost 0.
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Lists also carry pagination when the route pages.
Most products find an entity first, then deepen into detail and reviews only when needed.
GET /v1/airbnb/search?location=…PlaceList with priced stays
Pass dates and guests to price the stay you care about.
GET /v1/airbnb/listing?id=…&check_in=…&check_out=…Place with amenities, coordinates and a priced stay
Take the listing id from a search row.
GET /v1/airbnb/listing/reviews?id=…ReviewList with the host reply, up to 24 a page
data.total shows the full review count so a sample is never mistaken for the whole.
GET /v1/airbnb/listing/availability?id=…Night-by-night calendar for up to 12 months
Minimum stays and check-in rules sit on each night.
GET /v1/airbnb/search?location=Lisbon%2C+Portugal&check_in=2026-12-01&check_out=2026-12-05&adults=2
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here
GET /v1/airbnb/listing/reviews?id=33579922{
"success": true,
"data": {
"items": [
{
"place": {
"id": "33579922",
"name": "Example listing",
"rating": {
"value": 4.9
},
"hotel": {
"prices": {
"total": 640,
"currency": "EUR"
}
}
}
}
]
},
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}Field names match the rest of SocialCrawl where archetypes align. Parse once, reuse across platforms.
items[] with name, coordinates, rating, review count, photos, hotel.prices
title, category, description, amenities, check-in and check-out times, hotel.prices
items[] with rating, text, language, translated, date, guest, responses[]
nights[] with available, bookable, check-in and check-out flags, minimum and maximum stay
Same request lifecycle as every other /v1 platform endpoint. Airbnb is not a sidecar.
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).
Registry lookup finds the airbnb route. Required params and format checks run first. Invalid input returns 400 with no charge. Valid calls debit the tier cost atomically before the read starts.
A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: the public page is read live, with retries on 5xx or network errors and a circuit breaker if the source is unhealthy.
Airbnb data is mapped to the Place, PlaceList and ReviewList archetypes or returned as structured availability rows, validated, then wrapped in the success envelope and logged for billing audit.
Billing rules that matter in production
Airbnb is public read data. We normalize it into the SocialCrawl schema so your code does not learn a second vendor SDK.
Public listing pages, search results, guest reviews and availability calendars.
Public pages are read on request and normalized server-side. You never run an Airbnb login or booking session.
PlaceList and Place for listings, ReviewList for guest reviews, and structured rows for the calendar.
No booking, messaging, host tools or per-night calendar prices.
The jobs this API is most often used for.
Short-stay market research and review analysis
Callers search a market first, then read the listings that matter and pull their reviews and calendars. Priced stays, guest reviews with host replies and 12-month availability from one key, in the shared Place and Review schemas.
Live misses read the public page on request. Repeat calls hit cache and cost 0 credits.
Common ways teams put this data to work, and the stack each one tends to run.
search and listing with dates to benchmark nightly prices against nearby listings.
listing/availability to read how booked a market is across the next months.
listing/reviews to mine what guests praise and complain about.
Search is 1 credit. A page of reviews is 5. Cache hits are free.
curl "https://www.socialcrawl.dev/v1/airbnb/search?location=Lisbon%2C+Portugal&check_in=2026-12-01&check_out=2026-12-05&adults=2" \
-H "x-api-key: sc_your_api_key_here"curl "https://www.socialcrawl.dev/v1/airbnb/listing/reviews?id=33579922" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usAsk AI about SocialCrawl