/craigslist/postings

POST /api/craigslist/postings

Price: 1 credit

Get a full Craigslist posting by ID (or posting URL): title, price, complete body text, all category-specific attributes, the decoded VIN spec sheet for vehicles, hiring company for jobs, images, location with full address and coordinates, and posting dates.

How to use it

Fetch a single Craigslist posting by its ID (the 22-character id returned as `id` by craigslist/postings/search) or by a posting URL. Returns posting_title, price/price_string, description (plain text) and body_html, created_at/updated_at, section/category/category_alias, location (area, area_code, subarea, neighborhood, address, full_address, lat/lon), image/images and attributes — a list of key/label/value entries carrying the category-specific specs (make/model, odometer, condition, bedrooms, laundry, employment type and so on), each with the search_filters that reproduce it in craigslist/postings/search. Vehicles additionally carry vin_specs, the decoded VIN spec sheet (engine, drivetrain, body, safety systems); job postings carry company and is_open_to_recruiters. has_other_postings is true when the same seller has further postings, which craigslist/postings/seller then lists.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• posting string required — Craigslist posting ID or a posting URL containing it (examples: "unreSSL8PteC47PndGU6Ub", "https://www.craigslist.org/view/d/riverbank-2016-ford-explorer/unreSSL8PteC47PndGU6Ub"; minLength: 1)

Response

• @type string (default: "CraigslistPosting")
• id string required
• posting_id integer required
• posting_title string nullable
• url string nullable
• section string nullable
• category string nullable
• category_id integer nullable
• category_alias string nullable
• price number nullable
• price_string string nullable
• description string nullable
• body_html string nullable
• created_at integer nullable
• updated_at integer nullable
• has_contact_info boolean (default: false)
• has_other_postings boolean (default: false)
• is_open_to_recruiters boolean (default: false)
• company string nullable
• repost_of_id integer nullable
• location object nullable
  • @type string (default: "CraigslistPostingDetailLocation")
  • area_id integer nullable
  • area_alias string nullable
  • subarea_alias string nullable
  • description string nullable
  • neighborhood string nullable
  • lat number nullable
  • lon number nullable
  • area_code string nullable
  • area string nullable
  • subarea string nullable
  • address string nullable
  • full_address string nullable
  • location_type string nullable
• image string nullable
• images array (default: [])
• image_count integer (default: 0)
• attributes array (default: [])
  • @type string (default: "CraigslistPostingAttribute")
  • key string required
  • label string nullable
  • value string nullable
  • special_type string nullable
  • search_filters object (default: {})
    • * string
• vin_specs array (default: [])
  • @type string (default: "CraigslistPostingVinSpec")
  • group string required
  • key string required
  • value 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 — 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.