/manifold/markets/comments

POST /api/manifold/markets/comments

Price: 10 credits

Get the comments on a Manifold market, including replies

How to use it

Get the comments on a Manifold prediction market by market id, slug or URL, newest, oldest or most liked first. Replies are included and point at their parent through reply_to_comment_id; a comment posted with a trade carries that bet and the author's position at the time.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• market string required — Manifold market id, slug or URL (examples: "BpoEJNtlQoDBpfjBmK0y", "https://manifold.markets/AndrewG/will-republicans-win-the-senate-in-738388924521"; minLength: 1)
• count integer required — Max number of comments to return (examples: 50; min: 1)
• order string — Comment order (default: "newest"; one of: "newest", "oldest", "likes")

Response

• @type string (default: "ManifoldComment")
• id string required
• market_id string nullable
• market_alias string nullable
• market_question string nullable
• reply_to_comment_id string nullable
• answer_id string nullable
• text string nullable
• author object nullable
  • @type string (default: "ManifoldUserRef")
  • id string required
  • alias string nullable
  • name string nullable
  • url string nullable
  • image string nullable
  • is_bot boolean nullable
• like_count integer nullable
• comment_type string nullable
• visibility string nullable
• is_api boolean nullable
• is_repost boolean nullable
• is_hidden boolean nullable
• is_pinned boolean nullable
• pinner_id string nullable
• bet object nullable
  • @type string (default: "ManifoldCommentBet")
  • id string required
  • bettor_id string nullable
  • bettor_alias string nullable
  • bettor_name string nullable
  • answer_id string nullable
  • amount number nullable
  • order_amount number nullable
  • outcome string nullable
  • limit_probability number nullable
  • token string nullable
• author_position object nullable
  • @type string (default: "ManifoldCommentPosition")
  • outcome string nullable
  • shares number nullable
  • probability number nullable
  • answer_id string nullable
• reply_bet_amounts array (default: [])
  • @type string (default: "ManifoldOutcomeAmount")
  • outcome string required
  • amount number nullable
• created_at integer nullable
• edited_at integer nullable
• hidden_at integer nullable
• pinned_at 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 — Market 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.