/hemmings/listings/comments

POST /api/hemmings/listings/comments

Price: 1 credit

Get the public comment thread of a Hemmings listing: comments with text, author, like count, time, bid and offer flags, and nested replies.

How to use it

Read a Hemmings listing's comment thread by listing slug; replies are nested under their parent comment and count limits the top-level comments. Only Hemmings Auctions and make-offer listings, whose search URL is under /auction/ or /listing/, have a thread; rows under /classifieds/listing/, including third-party auctions with sale_type auction, have none and answer 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• listing string required — Listing slug from a hemmings.com/listing/<slug> or /auction/<slug> URL, or the URL itself (examples: "1966-ford-mustang-venice-fl-318539"; minLength: 1)
• count integer required — Max number of top-level comments to return (min: 1)

Response

• @type string (default: "HemmingsComment")
• id string required
• listing_alias string required
• parent_id string nullable
• text string nullable
• comment_type string nullable
• is_bid boolean nullable
• is_offer boolean nullable
• like_count integer nullable
• author object nullable
  • @type string (default: "HemmingsCommentAuthor")
  • id string required
  • name string nullable
  • is_member boolean nullable
• created_at integer nullable
• updated_at integer nullable
• replies 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 — No comment thread exists at this slug: the listing is unknown or is a /classifieds/listing/ row. 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.