Fanatics Live channel API

Endpoint facts

Method

GET

API path

/fanaticslive/channel/{id}

Auth

apiKey

Credits

1 credit/request

Platform

Fanatics Live

Response schema

#/definitions/fanaticslive.channelResponseDoc

Overview

Returns a Fanatics Live channel's own detail page: its parent shop, and a first page of its live/upcoming and past/replay shows. A shop can run several channels (e.g. a league-specific sub-feed) -- see /fanaticslive/shop/{slug} for a shop's full channel list and /fanaticslive/shop/{slug}/shows for cursor-paginated access to a full show history. Public data sourced from Fanatics Live'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

1 credit/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

- `live_shows` and `replay_shows` are each capped to a first page (no `after`/`limit` support on this endpoint) -- use [`GET /fanaticslive/shop/{slug}/shows`](fanaticslive-shop-shows.md) for full paginated access. - `live_shows[].status`/`replay_shows[].status` values: `ACTIVE`, `PREPARING`, `COMPLETE` -- see [`GET /fanaticslive/show/{id}`](fanaticslive-show.md) for the full status semantics. - An unrecognized `id` returns `404`. - A missing `id` returns `400` before any upstream request is made. Example response: ```json { "code": 200, "msg": "OK", "data": { "id": "adc4b55f-5e10-4ed0-8680-11875cfe1c94", "name": "Going Twice Pokemon", "shop": { "id": "81367b90-788a-4cf9-b2fd-e6c73f0a9174", "slug": "going-twice", "name": "Going Twice" }, "live_shows": [ { "id": "2c05ee77-3e37-46df-b998-bd509f80c8fd", "name": "Bingo Hall Wednesday w/ Fenrey & Mikey", "status": "PREPARING", "starts_at": "2026-09-23T14:30:00.000000Z", "channel": { "id": "adc4b55f-5e10-4ed0-8680-11875cfe1c94", "name": "Going Twice Pokemon", "shop": { "id": "81367b90-788a-4cf9-b2fd-e6c73f0a9174", "slug": "going-twice", "name": "Going Twice" } } } ], "replay_shows": [] } } ```

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