/coolapk/posts

POST /api/coolapk/posts

Price: 10 credits

Get a Coolapk community article (feed) by its id

How to use it

One Coolapk community post in full, by feed id or by a coolapk.com/feed/<id> URL, share token and all. Two shapes come back through the same fields: long articles, which carry a title, and photo or short posts, which have no title at all — both give the body as plain text and as HTML plus the inline image URLs, so a null title means a short post rather than a parsing failure. The post's age arrives as the source displays it, either a short Chinese date such as '8月4日' or a relative one such as '昨天' or '4天前', so read it as free text; created_at carries the exact moment in unix seconds. Long articles carry comments: up to 5 top comments (is_hot true) followed by up to 10 of the most recent ones, each with its first replies nested in replies, while reply_count carries the full total; short posts return an empty comments list. Feed ids come from coolapk/posts/editor-picks and coolapk/posts/official-reviews; an id that does not exist answers 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• feed_id string required — Coolapk feed id, or a coolapk.com/feed/<id> article URL (examples: "73077541", "https://www.coolapk.com/feed/73077541"; minLength: 1)

Response

• @type string (default: "CoolapkPost")
• feed_id string required
• title string nullable
• author_id string nullable
• author_name string nullable
• author_avatar string nullable
• created_at integer nullable
• published_text string nullable
• product_tag string nullable
• cover_image string nullable
• excerpt string nullable
• content_text string nullable
• content_html string nullable
• images array (default: [])
• topics array (default: [])
  • @type string (default: "CoolapkPostTopic")
  • name string required
  • url string nullable
• like_count integer nullable
• reply_count integer nullable
• favorite_count integer nullable
• share_count integer nullable
• forward_count integer nullable
• comment_count integer nullable
• ip_location string nullable
• feed_type string nullable
• comments array (default: [])
  • @type string (default: "CoolapkPostComment")
  • id string required
  • author_id string nullable
  • author_name string nullable
  • author_avatar string nullable
  • text string nullable
  • image string nullable
  • like_count integer nullable
  • reply_count integer nullable
  • created_at integer nullable
  • published_text string nullable
  • is_hot boolean (default: false)
  • is_author boolean (default: false)
  • reply_to_id string nullable
  • reply_to_name 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 — Feed 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.