/polymarket/events/comments

POST /api/polymarket/events/comments

Price: 5 credits

Get the comments under a Polymarket event by its id or slug

How to use it

Get the comment thread under a Polymarket event by its numeric id or slug. Returns each comment's text, author profile (name, pseudonym, bio, image, wallet), reactions, reaction and report counts, the parent comment id for replies, and created/updated timestamps. An event with no comments returns an empty list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• event string required — Event id (numeric) or slug (examples: "30615", "world-cup-winner"; minLength: 1)
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "PolymarketComment")
• id string required
• text string required
• parent_comment_id string nullable
• user_address string nullable
• reply_address string nullable
• profile object nullable
  • @type string (default: "PolymarketCommentProfile")
  • name string nullable
  • pseudonym string nullable
  • bio string nullable
  • image string nullable
  • proxy_wallet string nullable
  • base_address string nullable
  • display_username_public boolean nullable
• reactions array (default: [])
  • @type string (default: "PolymarketCommentReaction")
  • reaction_type string required
  • proxy_wallet string nullable
• reaction_count integer nullable
• report_count integer nullable
• created_at string nullable
• updated_at 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 — Event not found 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.