Get a TicketWeb event API

Endpoint facts

Method

GET

API path

/ticketweb/event

Auth

apiKey

Credits

1 credit/request

Platform

TicketWeb

Response schema

#/definitions/ticketweb.eventResponseDoc

Overview

Returns normalized details for one TicketWeb event: venue, dates, age restriction, delivery methods, and per-tier ticket pricing (base price, fee breakdown, and total) when tickets are on sale. `has_tickets` is false and `sections` is empty for a free/RSVP event with no paid tickets, a sold-out event, or an access-code-gated event -- TicketWeb's own data does not reliably distinguish these three cases at this level, so the response reports the shared observable state (no purchasable sections) rather than guessing which applies. 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

- `sections` lists each ticket tier (e.g. "GA Standing", "Reserved Seating"), each with one or more `prices`. Every price reports `base` (pre-fee face value), a `fees` breakdown, and `total` (the amount TicketWeb actually charges -- `base` plus every `fees` component). - `price_range` is the event's page-level min/max `total` across all tiers, matching the range shown near TicketWeb's own buy button. It is omitted when the event has no purchasable tickets. - `has_tickets` is `false` and `sections` is empty for three distinct upstream states TicketWeb does not reliably distinguish at this level: a free/RSVP event with no paid tickets, a sold-out event, and an access-code-gated event. The response reports the shared observable state (no purchasable sections) rather than guessing which applies -- see `notes/ticketweb-maintenance.md` for the live samples behind this. - `start_time`, `on_sale_time`, and `announce_time` carry TicketWeb's own timezone-offset timestamps (e.g. `2026-08-25T19:30:00.000-05:00`) when the upstream event has them set. - A nonexistent id currently returns a `503` upstream error (TicketWeb serves a generic block/challenge shell for a bad id rather than a distinguishable 404) -- treat a `503` for a freshly-looked-up id as "check the id" as well as "retry later". Example response: ```json { "code": 200, "msg": "OK", "data": { "source_url": "https://www.ticketweb.com/event/comedy-beast-howlin-wolf-tickets/14241184", "fetched_at": "2026-08-24T18:00:00Z", "event": { "id": "14241184", "name": "Comedy Beast", "url": "https://www.ticketweb.com/event/comedy-beast-howlin-wolf-tickets/14241184", "start_time": "2026-08-25T19:30:00.000-05:00", "on_sale_time": "2026-07-01T12:05:00.000-05:00", "age_restriction": 18, "age_restriction_message": "Ages 18+", "venue": { "id": "15005", "name": "Howlin' Wolf", "address": "907 South Peters", "city": "New Orleans", "state": "LA", "postal_code": "70130", "country": "US", "time_zone": "US/Central" }, "attractions": [ { "name": "Comedy Beast", "category": "Arts & Theater", "genre": "Comedy" } ], "delivery_methods": [ { "name": "eTickets", "description": "Display on your mobile device or print out your ticket for entry!", "fee": "Free" } ], "currency": "USD", "has_tickets": true, "price_range": { "min": 8.16, "max": 8.16 }, "sections": [ { "name": "GA Seating", "sold_out": false, "purchase_limit": 10, "prices": [ { "name": "GA Seating", "base": 5, "fees": { "credit_card": 0.16, "per_ticket": 1.5, "rebate": 1.5 }, "total": 8.16, "sold_out": false, "max_purchase_limit": 10 } ] } ] } } } ```

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