Get WeChat MP article comments (single page, `buffer` cursor pagination); returns one page of featured comments. Pagination: leave `buffer` empty for the first page → take `buffer` from the response → pass it back in the next request; `has_more` false means the last page. For second-level replies of a specific comment, use `fetch_comment_replies` (pass the comment's `content_id`). Price: $0.01 per request ⏱️ Due to WeChat server latency, this endpoint responds slowly; please set your client request timeout to 30 seconds — a timeout that is too small may result in being billed without receiving the response. ⚠️ Large-integer ID precision: IDs such as `content_id` in the response are 64-bit big integers beyond JavaScript's safe-integer range (2^53-1). Always receive / pass such IDs as strings (parse JSON with json-bigint or read them as text), never through JS `Number`. Swagger UI rounds the trailing digits of huge integers in its docs view — this is expected and does not affect the actual data returned by the API.
Request body
Call this sync operation at its vendor-qualified URL. The model identity is encoded in the path; only operation-specific input fields belong in the request body.
Optional<string | null>buffer
Optional, default empty. Pagination cursor; leave empty for the first page, pass `buffer` from the previous response for the next page.
Default: ""
Optional<boolean>raw
Optional, default True. True=full raw comment objects; False=simplified comment view.
Default: true
stringurlrequired
WeChat MP article URL (`https://mp.weixin.qq.com/s/…`). E.g. `https://mp.weixin.qq.com/s/TSNQKkRpN1qbKsT7BvzqIw`
Length: 0 to 2048. Pattern: ^https?://mp\.weixin\.qq\.com/s([/?].+)?$
Response Schema
A synchronous completed response contains exactly one outputs item with only data. Failed and timeout responses contain error and never outputs.
stringidrequired
Opaque SandBase run identifier. Use it exactly as returned; no prefix is guaranteed.
Get WeChat MP Article Comments
/v1/api/wechat-mp/v2/article-commentsGet WeChat MP article comments (single page, `buffer` cursor pagination); returns one page of featured comments. Pagination: leave `buffer` empty for the first page → take `buffer` from the response → pass it back in the next request; `has_more` false means the last page. For second-level replies of a specific comment, use `fetch_comment_replies` (pass the comment's `content_id`). Price: $0.01 per request ⏱️ Due to WeChat server latency, this endpoint responds slowly; please set your client request timeout to 30 seconds — a timeout that is too small may result in being billed without receiving the response. ⚠️ Large-integer ID precision: IDs such as `content_id` in the response are 64-bit big integers beyond JavaScript's safe-integer range (2^53-1). Always receive / pass such IDs as strings (parse JSON with json-bigint or read them as text), never through JS `Number`. Swagger UI rounds the trailing digits of huge integers in its docs view — this is expected and does not affect the actual data returned by the API.
Request body
Call this sync operation at its vendor-qualified URL. The model identity is encoded in the path; only operation-specific input fields belong in the request body.
bufferOptional, default empty. Pagination cursor; leave empty for the first page, pass `buffer` from the previous response for the next page.
Default:
""rawOptional, default True. True=full raw comment objects; False=simplified comment view.
Default:
trueurlrequiredWeChat MP article URL (`https://mp.weixin.qq.com/s/…`). E.g. `https://mp.weixin.qq.com/s/TSNQKkRpN1qbKsT7BvzqIw`
Length: 0 to 2048. Pattern: ^https?://mp\.weixin\.qq\.com/s([/?].+)?$
Response Schema
A synchronous completed response contains exactly one outputs item with only data. Failed and timeout responses contain error and never outputs.
idrequiredOpaque SandBase run identifier. Use it exactly as returned; no prefix is guaranteed.
statusrequiredCurrent public run status.
Allowed values: pending, running, completed, failed, timeout
modelrequiredPublic SandBase model name used for this run.
outputsPresent only for completed runs. Contains exactly one item whose only field is data.
outputs[0].dataOperation-specific business payload. This reference uses an empty object when no safe example can be confirmed.
errorPresent only for failed or timeout runs. Contains a public error type and sanitized message.
error.typeStable public error category.
error.messageSanitized error message safe to show to clients.
usageUsage details when available.
API capabilities
capability_tagsrequiredCapabilities declared by the API registry.
Default:
api, wechat-mpexecution_moderequiredExecution mode declared by the API registry.
Default:
syncpending response
{"id":"f3d2e8a1-7c4b-4a12-9d2e-123456789abc","status":"pending","model":"wechat-mp/v2/article-comments"}
running response
{"id":"f3d2e8a1-7c4b-4a12-9d2e-123456789abc","status":"running","model":"wechat-mp/v2/article-comments"}
completed response
{"id":"f3d2e8a1-7c4b-4a12-9d2e-123456789abc","status":"completed","model":"wechat-mp/v2/article-comments","outputs":[{"data":{}}]}
failed response
{"id":"f3d2e8a1-7c4b-4a12-9d2e-123456789abc","status":"failed","model":"wechat-mp/v2/article-comments","error":{"type":"upstream_error","message":"upstream request failed"}}
timeout response
{"id":"f3d2e8a1-7c4b-4a12-9d2e-123456789abc","status":"timeout","model":"wechat-mp/v2/article-comments","error":{"type":"upstream_error","message":"upstream request failed"}}