Twitch VOD comments (chat replay) API

Endpoint facts

Method

GET

API path

/twitch/vod-comments

Auth

apiKey

Credits

2 credits/request

Platform

Twitch

Response schema

#/definitions/twitch.vodCommentsResponseDoc

Overview

Returns one page of a Twitch VOD's chat replay (past-broadcast chat messages), starting at a given point in the video's timeline. Paginate forward by re-requesting with the last returned comment's offset_seconds. Public data sourced from Twitch's own GraphQL API. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

2 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- Pagination is offset-based only: use the last returned comment's `offset_seconds` (or `next_offset_seconds`) as the next request's `offset` to page forward. Twitch's own cursor-based paging mode for this operation requires a device-integrity token this endpoint does not carry, so it is not exposed here. - `message` is the comment's flattened plain text; `fragments` breaks it into text/emote runs, with `emote_id` set on emote fragments. - `has_more` reflects whether Twitch has additional comments after this page's last offset. - A video with no chat replay data (or that never had chat) returns a `200` with an empty `comments` list. - An unknown video id returns `404`. A missing `video` returns `400` before any upstream request is made. Example response: ```json { "code": 200, "msg": "OK", "data": { "video_id": "2845804307", "offset_seconds": 0, "count": 55, "has_more": true, "next_offset_seconds": 140, "comments": [ { "id": "d19286b9-dd9c-45b7-91eb-1fff28926f2c", "commenter": { "id": "271911711", "login": "mrfluffernuts", "display_name": "mrfluffernuts" }, "offset_seconds": 53, "created_at": "2026-08-14T07:19:45.217Z", "message": "I'm going to spend my 50million during game 5 of worlds so you have to end stream @caedrel", "fragments": [ { "text": "I'm going to spend my 50million during game 5 of worlds so you have to end stream @caedrel" } ] } ] } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related