POST /api/nextdoor/businesses
Price: 1 credit
Get Nextdoor business
Get a Nextdoor business or agency page by country and slug. Returns name, categories, phone, email, website, address, business hours, opening status, photo gallery, neighborhood favorites won, recommendation summary, and favorite count.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)country string — Nextdoor country/region (default: "US"; one of: "US", "GB", "DE", "FR", "IT", "ES", "AU", "DK", "SE", "CA", "NL")slug string required — Business page slug or /pages/ URL (examples: "trabocco-alameda-ca"; minLength: 1)@type string (default: "NextdoorBusiness")id string nullablealias string nullablename string nullabledescription string nullablephone string nullableemail string nullablewebsite_url string nullableurl string nullablelicense_id string nullablelocation_status string nullablefave_count integer nullablerecommendation_summary string nullableis_takeout_offered boolean nullableis_delivery_offered boolean nullableimage string nullablecover string nullablecategories array (default: [])centroid object nullable@type string (default: "NextdoorGeoPoint")lat number nullablelon number nullableaddress object nullable@type string (default: "NextdoorAddress")street_number string nullableroute string nullableunit_number string nullablecity string nullablestate string nullablestate_name string nullablepostal_code string nullablecountry string nullableformatted string nullableopen_status string nullablehours array (default: [])@type string (default: "NextdoorBusinessHours")day string nullableintervals array (default: [])gallery array (default: [])gallery_count integer nullableyears_won array (default: [])neighborhoods_won array (default: [])@type string (default: "NextdoorNeighborhoodWon")name string nullablecity string nullableurl string nullabledelivery_services array (default: [])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 — Business not found. Verify country and slug. 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.