/airbnb/hosts

POST /api/airbnb/hosts

Price: 1 credit

Get an Airbnb host (user) profile by host id (or profile URL): name, photo, superhost and identity verification status, host rating and review count, location, about text, hosting tenure, past trips, identity verifications, interests, and the host's managed listings (each with name, photo, room and property type, rating, reviews and capacity) plus the total listing count.

How to use it

Fetch a single Airbnb host profile by numeric host id or a /users/show/ URL. Returns one item with id, url, name, image, is_superhost, is_verified, is_home_host, rating, review_count, location, about, years_hosting, months_hosting, verified_since, past_trips_count, identity_verifications, interests, listing_count and listings (id, url, name, image, room_type, property_type, rating, review_count, bedroom_count, bed_count, bathroom_count, is_superhost).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• host string required — Airbnb host (user) id or a host profile URL containing it (examples: "488373990", "https://www.airbnb.com/users/show/488373990"; minLength: 1)

Response

• @type string (default: "AirbnbHostProfile")
• id string required
• url string nullable
• name string nullable
• image string nullable
• is_superhost boolean nullable
• is_verified boolean nullable
• is_home_host boolean nullable
• rating number nullable
• review_count integer nullable
• location string nullable
• about string nullable
• years_hosting integer nullable
• months_hosting integer nullable
• verified_since string nullable
• past_trips_count integer nullable
• identity_verifications array (default: [])
• interests array (default: [])
• listing_count integer nullable
• listings array (default: [])
  • @type string (default: "AirbnbHostListing")
  • id string required
  • url string nullable
  • name string nullable
  • image string nullable
  • room_type string nullable
  • property_type string nullable
  • rating number nullable
  • review_count integer nullable
  • bedroom_count integer nullable
  • bed_count integer nullable
  • bathroom_count number nullable
  • is_superhost boolean nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Host not found, private or inaccessible profile (well-formed but nonexistent/withdrawn host id) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.