/nextdoor/topics

POST /api/nextdoor/topics

Price: 1 credit

Get Nextdoor local topic recommendations

How to use it

Get local recommendation questions and neighbor answers for a topic in a city (e.g. best coffee, italian restaurants). Returns question posts with their answers, each including the answer text, author, neighborhood, timestamp and reaction count, plus the other topic and resource pages that exist for the same city.

Parameters

• access-token string required

Request body

• timeout 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")
• state string required — State or region code (examples: "ca"; minLength: 1)
• city string required — City slug (examples: "berkeley"; minLength: 1)
• topic string required — Topic question (examples: "best-coffee", "italian-restaurants"; minLength: 1)

Response

• @type string (default: "NextdoorTopic")
• topic string nullable
• city string nullable
• state string nullable
• full_state_name string nullable
• hero_image string nullable
• description string nullable
• posts array (default: [])
  • @type string (default: "NextdoorTopicPost")
  • author_name string nullable
  • author_type string nullable
  • author_url string nullable
  • image string nullable
  • text string nullable
  • created_at integer nullable
  • comment_count integer nullable
  • reaction_count integer nullable
  • answers array (default: [])
    • @type string (default: "NextdoorTopicAnswer")
    • author_name string nullable
    • author_neighborhood string nullable
    • location_hint string nullable
    • text string nullable
    • created_at integer nullable
    • reaction_count integer nullable
• related_topics array (default: [])
  • @type string (default: "NextdoorLink")
  • name string nullable
  • url string nullable
• city_resources array (default: [])
  • @type string (default: "NextdoorLink")
  • name string nullable
  • url string 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 — Topic not found. Verify country, state, city, and topic. 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.