/carsandbids/auctions/comments

POST /api/carsandbids/auctions/comments

Price: 5 credits

Get the comment thread of a Cars & Bids auction: comments and bids with text, bid amount, author with seller/bidder/verified flags and reputation, reply target, upvotes, pinned flag, time and attached images.

How to use it

Read an auction's thread by auction id. view picks newest (comments and bids together), most_upvoted, seller_comments or bid_history; a bid row carries bid_amount.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• auction string required — Auction id, the token after /auctions/ in the auction URL, or the full auction URL (examples: "9lYm0eX5"; minLength: 1)
• view string required — newest: comments and bids, newest first; most_upvoted; seller_comments: the seller's own comments; bid_history: bids only (one of: "newest", "most_upvoted", "seller_comments", "bid_history")
• count integer required — Max number of comments and bids to return (min: 1)

Response

• @type string (default: "CarsandbidsComment")
• id string required
• auction_id string required
• comment_type string nullable
• text string nullable
• bid_amount number nullable
• author object nullable
  • @type string (default: "CarsandbidsUser")
  • id string nullable
  • alias string required
  • url string required
  • image string nullable
  • is_certified_seller boolean nullable
  • is_seller boolean nullable
  • is_bidder boolean nullable
  • is_verified boolean nullable
  • is_staff boolean nullable
  • reputation integer nullable
  • follower_count integer nullable
• reply_to object nullable
  • @type string (default: "CarsandbidsCommentReply")
  • id string required
  • author_alias string nullable
• upvote_count integer nullable
• flag_count integer nullable
• is_pinned boolean (default: false)
• is_system_flagged boolean nullable
• created_at integer nullable
• updated_at integer nullable
• edited_at integer nullable
• deleted_at integer nullable
• images array (default: [])
  • @type string (default: "CarsandbidsPhoto")
  • id string nullable
  • category string nullable
  • image string required
  • width integer nullable
  • height integer 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 — No Cars & Bids auction exists with this 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.