/maimai/posts

POST /api/maimai/posts

Price: 5 credits

Get one real-name Maimai post by URL or id plus efid: text, images, video, author name and headline, reactions, engagement counts and topics

How to use it

Takes a maimai.cn feed-detail link, or the post id with its efid.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• post string required — Maimai post URL or numeric post id (examples: "https://maimai.cn/community/feed-detail/1917764167?efid=cksukG5wKckRPeK0MiFzZQ&fid=1917764167", "1917764167")
• efid string nullable — Post access token, required with a bare id (examples: "cksukG5wKckRPeK0MiFzZQ")

Response

• @type string (default: "MaimaiPost")
• id string required
• efid string required
• url string required
• text string nullable
• images array (default: [])
• video object nullable
  • @type string (default: "MaimaiVideo")
  • url string required
  • thumbnail string nullable
  • width integer nullable
  • height integer nullable
  • duration number nullable
  • size_bytes integer nullable
• published_at integer nullable
• ip_location string nullable
• like_count integer nullable
• comment_count integer nullable
• share_count integer nullable
• reactions array (default: [])
  • @type string (default: "MaimaiReaction")
  • name string required
  • code string nullable
  • count integer nullable
• author object nullable
  • @type string (default: "MaimaiPostAuthor")
  • id string nullable
  • name string nullable
  • image string nullable
  • headline string nullable
  • custom_title string nullable
  • medal string nullable
• topics array (default: [])
  • @type string (default: "MaimaiTopic")
  • id string required
  • name string nullable
• attitudes array (default: [])
  • @type string (default: "MaimaiAttitude")
  • id string required
  • text string nullable
  • is_positive boolean required
  • count integer nullable
• declaration 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 — No post with that id and efid 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.