Search events (legacy)
/v0.3.1/events/searchLegacy 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'inevent_datematches all 2023 events). - All body properties are optional.
- Use
historical=trueto 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_idorstd_event_idvia the v1 search endpoint.
Caveat:
venue_nameandvenue_statemay contain non-standard values (e.g., "CA" or "Cal" for California). For standardized values, use the v1 search endpoint.
Pass Authorization: Bearer <api_key>. Preferred for new integrations.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
curl -X POST "https://example.com/v0.3.1/events/search" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "event_name": "Taylor Swift", "venue_city": "Cincinnati" }'[ { "result_total": 1, "items": [ { "event_id": 45558, "event_name": "Taylor Swift", "event_date": "2023-04-25", "venue_name": "AT&T Park", "venue_city": "San Francisco", "venue_state": "CA" } ], "errors": false }]Get listings GET
All 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).
Request event add POST
Submit a search query to find and add events to the SeatData platform. Returns a job ID used to check status. **Notes:** - Maximum 5 simultaneous jobs (pending or processing) per user - Maximum query length: 200 characters - Allowed characters: alphanumeric, spaces, basic punctuation (`a-zA-Z0-9 -_.,'"&`)