/craigslist/postings/seller

POST /api/craigslist/postings/seller

Price: 10 credits

List every Craigslist posting published by the seller of a given posting: the full inventory of a dealer, landlord or shop, with title, price, location, images and posting date for each result.

How to use it

List all postings of one Craigslist seller. Craigslist has no public seller profile, so the seller is identified by the ID of any one of their postings (the `id` returned by craigslist/postings/search and craigslist/postings); the area is resolved from that posting. Returns the same posting cards as craigslist/postings/search, including the posting you passed in. Sellers who published only that one posting return an empty list — craigslist/postings reports this upfront as has_other_postings=false.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• posting string required — ID of any posting of that seller, or a posting URL containing it (examples: "oFhGw4aD8RGJiaKaCXFU2g"; minLength: 1)
• count integer required — Max number of postings to return (min: 1; max: 10000)
• category string nullable — Category alias to look in, from craigslist/categories (examples: "sss")
• sort string — Result ordering (default: "newest"; one of: "newest", "oldest", "price_asc", "price_desc", "distance", "relevance", "upcoming")

Response

• @type string (default: "CraigslistPostingCard")
• id string required
• posting_id integer required
• posting_title string nullable
• alias string nullable
• url string nullable
• price number nullable
• price_string string nullable
• currency string nullable
• monthly_payment_string string nullable
• created_at integer nullable
• category_id integer nullable
• category_alias string nullable
• category string nullable
• location object nullable
  • @type string (default: "CraigslistPostingLocation")
  • area_id integer nullable
  • area_alias string nullable
  • subarea_alias string nullable
  • description string nullable
  • neighborhood string nullable
  • lat number nullable
  • lon number nullable
• image string nullable
• images array (default: [])
• image_count integer (default: 0)
• bedrooms number nullable
• sqft number nullable
• auto_miles number nullable
• salary string nullable
• company string nullable
• job_title string nullable
• start_date string nullable
• end_date string nullable
• open_house_dates array (default: [])
• event_dates array (default: [])

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 — Posting not found (well-formed but nonexistent, expired or removed posting 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.