Search Events · Events API
Run one live Events search and receive individual events for a query, including title, dates, venue location, ticket links, and a description.
Using ChatGPT, Claude Code or another client? See the setup steps
curl -X POST https://api.unifapi.com/events/search \ -H "Authorization: Bearer $UNIFAPI_KEY" \ -H "Content-Type: application/json"
This operation is part of the Events API in the events category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.
Use it when a workflow needs Events public data alongside maps, hotels or local listings, but should still keep one API key, one account balance, and one predictable JSON contract.
Common agent workflows
- Search Events for public mentions, creators, posts, or topics matching a user query.
- Feed ranked Events results into research, monitoring, and enrichment workflows.
- Give an AI agent a stable Events data source without building a per-platform integration.
- Normalize Events responses into the same UnifAPI envelope used across the catalog.
Unified envelope, platform-native fields
- List-style responses return `data` as an array of top-level records plus optional `pagination` for continuation tokens or cursors.
- The operation has a 10 credits ($0.01) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
- If the workspace balance cannot cover every result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.
Response status codes
Billing
This operation charges 1 credit per billable record, with a 10 credits ($0.01) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.
Errors and retries
Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.
Fields in the data object
A successful Search Events call returns one data object with these fields.
- querystring
- locationstring
- languagestring
- viewstring
- observed_atstring
- search_urlstring
- item_typesstring[]
- SERP element types present in the result, in source order.
- total_resultsinteger
- result_countinteger
- Number of result elements returned.
- resultsobject[]
- Individual events results flattened from the events block. Each event is one billable record; date, venue, and ticket details are carried in extras.
More Events operations
Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.