/bringatrailer/listings/comments

POST /api/bringatrailer/listings/comments

Price: 5 credits

Get the comment thread of a Bring a Trailer listing, newest first: comments, bids and BaT notices with text, bid amount, author with their like count, likes and dislikes, reply target, edited and featured flags, time and attached images.

How to use it

Read a Bring a Trailer listing's thread by listing slug. comment_type tells a comment from a bat-bid row, which carries bid_amount, and from BaT's own notices.

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 bringatrailer.com/listing/<slug>/ URL, or the URL itself (examples: "1962-chevrolet-impala-ss-57"; minLength: 1)
• count integer required — Max number of comments and bids to return (min: 1)

Response

• @type string (default: "BringatrailerComment")
• id string required
• listing_id string nullable
• comment_type string nullable
• text string nullable
• bid_amount number nullable
• author object nullable
  • @type string (default: "BringatrailerCommentAuthor")
  • id string nullable
  • alias string nullable
  • name string nullable
  • url string nullable
  • like_count integer nullable
  • is_deleted boolean nullable
• parent_id string nullable
• like_count integer nullable
• dislike_count integer nullable
• is_featured boolean nullable
• is_edited boolean nullable
• created_at integer nullable
• images 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 Bring a Trailer listing exists at this 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.

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.