Whatnot live API

Endpoint facts

Method

GET

API path

/whatnot/live/{id}

Auth

apiKey

Credits

3 credits/request

Platform

Whatnot

Response schema

#/definitions/whatnot.liveResponseDoc

Overview

Returns a Whatnot live show's current shop feed: every product, auction, and giveaway listing currently visible in the show, each with its seller's rating. Public data sourced from Whatnot'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

3 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

- `transaction_type` distinguishes how a listing is sold: `AUCTION` (bid-based, `current_bid_cents`/`current_bid_count` populated once bidding starts), `GIVEAWAY`, or `BUY_NOW`. - `status` reflects the listing's own lifecycle (e.g. `created`, `running`, `sold`), not the show's overall live/ended state. - `seller.rating`/`seller.review_count` are scoped to the listing's seller, not the requester — there is no separate seller-profile lookup this endpoint calls. - An unknown or ended show id returns `200` with `"products": []`, not an error — Whatnot's own backend doesn't distinguish "no such show" from "a real show with nothing currently listed." - A missing `id` returns `400` before any upstream request is made. Example response: ```json { "code": 200, "msg": "OK", "data": { "id": "6ddb7fd2-43bb-44e0-8ee8-6656e82fa26a", "url": "https://www.whatnot.com/live/6ddb7fd2-43bb-44e0-8ee8-6656e82fa26a", "products": [ { "id": "TGlzdGluZ05vZGU6MjEzMTA5NzI1NA==", "title": "slab", "description": "show live", "price_cents": 1000, "currency": "USD", "status": "running", "transaction_type": "AUCTION", "quantity": 219, "seller": { "username": "legacy_auction_house", "rating": 4.9, "review_count": 128914 } } ] } } ```

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