Get listings
/v0.1.1/listings/getAll responses are gzip encoded.
You must pass either a SeatData Event ID (from the search endpoints) or a Marketplace Event ID (obtained separately).
You are not charged for calls where the listings data has not
refreshed since your last pull. The has_refreshed field in the
response indicates whether new data was returned (and therefore
whether the call counts toward billing).
Pass Authorization: Bearer <api_key>. Preferred for new integrations.
In: header
Query Parameters
SeatData Event ID
Marketplace Event ID
Response Body
application/json
curl -X GET "https://example.com/v0.1.1/listings/get?event_id=225220" \ -H "Authorization: Bearer YOUR_API_KEY"{ "has_refreshed": 1, "last_refresh_timestamp": 1709505600, "listings": [ { "listing_id": 7300750943, "active": true, "zone": "Upper Level", "section": "Upper 216", "row": "12", "quantity_start": 4, "quantity": 2, "price": 66.45 } ]}Get sales data (batch) POST
All responses are gzip encoded. Accepts up to 100 events per request, combined across both id lists after deduplication. Billing is identical to `GET /v0.3/salesdata/get` — one pull per event that returns sales data; events with no sales are free. `results` is keyed by the identifier you sent: Marketplace Event IDs appear under the marketplace id, SeatData Event IDs under the SeatData id. `errors` reports per-event failures: `not_found` for a SeatData Event ID that does not exist, `payment_required` when a pay-as-you-go balance ran out mid-batch (that event's data is withheld; events already charged are still returned).
Search events (legacy) POST
Legacy event search (POST) - for new integrations, prefer `GET /v1/events/search`. Searches SeatData events. Returns the SeatData Event ID needed for the salesdata, listings, and v1 stats endpoints. - All search fields are case-insensitive. - Partial strings will be matched, including dates (e.g., `'2023'` in `event_date` matches all 2023 events). - All body properties are optional. - Use `historical=true` to search events before the current date. - No charge per call. > **Note:** Searches with non-Western characters (Cyrillic, CJK, > Greek, etc.) return an empty result. For multilingual lookup, > use `tm_event_id` or `std_event_id` via the v1 search endpoint. > **Caveat:** `venue_name` and `venue_state` may contain > non-standard values (e.g., "CA" or "Cal" for California). For > standardized values, use the v1 search endpoint.