Get WeChat Channels Live History
/v1/api/wechat-channels/v2/live-historyGet a creator's live replay list. Each replay is itself a video object with a `media` object (`url` / `url_token` / `decode_key`) ready for download and decryption. Supports pagination for more replays. 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 `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 fetch flag, default 12.
Range: 0 to 1000
Optional pagination cursor (base64), **leave empty for the first page**; when `continue_flag` is truthy, pass the previous page's `last_buffer`.
Optional, default True. True=raw response; False=simplified parsed structure (recommended for media download).
WeChat Channels finder username (`v2_…@finder` format). Example (an account with live replays): `v2_060000231003b20faec8cae1811ac4d5c702ea32b0771737aa785454f7f8177114cc4d248d66@finder` (Huxiu).
Length: 10 to 256. Pattern: ^v2_[0-9a-fA-F]+@finder$
Response Schema
A synchronous completed response contains exactly one outputs item with only data. Failed and timeout responses contain error and never outputs.
Opaque SandBase run identifier. Use it exactly as returned; no prefix is guaranteed.
Current public run status.
Allowed values: pending, running, completed, failed, timeout
Public SandBase model name used for this run.
Present only for completed runs. Contains exactly one item whose only field is data.
Operation-specific business payload. This reference uses an empty object when no safe example can be confirmed.
Present only for failed or timeout runs. Contains a public error type and sanitized message.
Stable public error category.
Sanitized error message safe to show to clients.
Usage details when available.
API capabilities
Capabilities declared by the API registry.
Default: api, wechat-channels
Execution mode declared by the API registry.
Default: sync
pending response
{"id":"f3d2e8a1-7c4b-4a12-9d2e-123456789abc","status":"pending","model":"wechat-channels/v2/live-history"}
running response
{"id":"f3d2e8a1-7c4b-4a12-9d2e-123456789abc","status":"running","model":"wechat-channels/v2/live-history"}
completed response
{"id":"f3d2e8a1-7c4b-4a12-9d2e-123456789abc","status":"completed","model":"wechat-channels/v2/live-history","outputs":[{"data":{}}]}
failed response
{"id":"f3d2e8a1-7c4b-4a12-9d2e-123456789abc","status":"failed","model":"wechat-channels/v2/live-history","error":{"type":"upstream_error","message":"upstream request failed"}}
timeout response
{"id":"f3d2e8a1-7c4b-4a12-9d2e-123456789abc","status":"timeout","model":"wechat-channels/v2/live-history","error":{"type":"upstream_error","message":"upstream request failed"}}