/maimai/gossips/comments

POST /api/maimai/gossips/comments

Price: 5 credits

Get the first comments of a Maimai gossip by URL or id plus egid: text, author nickname and headline, likes, reply count and the replies shown under each comment

How to use it

Returns at most the first 10 top-level comments, in the site's own order, each with the replies shown under it. Takes the same gossip link or id plus egid as maimai/gossips.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• gossip string required — Maimai gossip URL or numeric gossip id (examples: "https://maimai.cn/community/gossip-detail/37808738?egid=44fa44d57250423184b867d46e19a74d", "37808738")
• egid string nullable — Gossip access token, required with a bare id (examples: "44fa44d57250423184b867d46e19a74d")
• count integer required — Number of comments to return (examples: 10; min: 1; max: 10)

Response

• @type string (default: "MaimaiComment")
• id string required
• gossip_id string required
• text string nullable
• time_text string nullable
• ip_location string nullable
• like_count integer nullable
• reply_count integer nullable
• is_pinned boolean nullable
• is_by_author boolean nullable
• reply_to_name string nullable
• author object nullable
  • @type string (default: "MaimaiCommentAuthor")
  • name string nullable
  • image string nullable
  • headline string nullable
  • is_verified boolean nullable
  • medal string 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 gossip with that id and egid 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.