canonical: https://jentic.com/apis/oveit.com/oveit

# Oveit API

Oveit is an event registration and ticketing platform that simplifies attendee management, ticket sales, check-in, and RFID integration for events. The API provides endpoints for seller authentication, event management, ticket and attendee retrieval, ticket import, check-in and scanning, RFID pairing, addon management, and attendee data export. Use it to automate event setup, integrate ticketing with CRM and marketing tools, build custom check-in apps, manage RFID-enabled access control, and export attendee data for post-event analysis.

## For AI agents

Manage Oveit events, tickets, attendees, check-ins, RFID pairing, and addons for event registration and access control automation.

## Scope

Does not handle payment processing, email marketing, or venue booking - use for ticketing, attendee management, check-in, and RFID workflows only.

## Capabilities

- Authenticate sellers and manage session tokens
- List and retrieve events associated with a seller account
- Retrieve attendees for specific events with pagination
- List tickets and ticket types for events
- Import tickets in bulk for event setup
- Check in attendees by scanning tickets
- Scan tickets for validation and access control
- Pair RFID wristbands or badges with tickets for contactless access
- Enable and disable ticket addons (upsells, extras) programmatically
- Export attendee data files for analysis or CRM sync

## Use cases

### Automated Event Check-In and Access Control

Build custom check-in workflows using ticket scanning and RFID pairing. POST `/tickets/scan` validates a ticket by barcode or QR code, POST `/tickets/checkin` marks the attendee as checked in, and POST `/rfid/pair` associates an RFID wristband with a ticket for contactless access. This powers mobile check-in apps, self-service kiosks, and multi-entrance validation systems, reducing wait times and manual check-in overhead at event entrances.

Example prompt: POST `/tickets/scan` with ticket barcode to validate, then POST `/tickets/checkin` to mark as checked in. Use POST `/rfid/pair` with ticket_id and RFID tag to enable contactless access.

### Attendee Data Export and CRM Integration

Sync event attendee data with CRM, marketing automation, or analytics platforms. GET `/events/attendees` retrieves all attendees for an event with contact details, ticket type, and purchase info. GET `/attendees/download_file` exports attendee data in bulk for post-event follow-up campaigns, lead scoring, or event performance analysis. Automate this sync to trigger thank-you emails, add attendees to CRM pipelines, or feed engagement data to BI dashboards.

Example prompt: GET `/events/attendees` to retrieve attendee records, then export via GET `/attendees/download_file.` Push data to CRM or email marketing platform for post-event engagement.

### Bulk Ticket Import and Event Setup

Automate event setup by importing tickets in bulk from external systems or spreadsheets. POST `/tickets/import` accepts ticket data (name, email, ticket type) and creates attendee records programmatically. This supports migrations from other ticketing platforms, corporate event registrations managed in HR systems, or sponsor-provided guest lists. Eliminate manual ticket entry and accelerate event launch.

Example prompt: POST `/tickets/import` with an array of attendee details (name, email, ticket_type) to create tickets in bulk. Use for migrations or sponsor guest list integration.

### Addon and Upsell Management

Enable or disable ticket addons (merchandise, VIP upgrades, meal vouchers) dynamically based on purchase or refund events. POST `/tickets/enable_addon` adds an addon to a ticket, and POST `/tickets/disable_addon` removes it. Integrate with e-commerce, payment gateways, or customer support tools to automatically provision or revoke addons when purchases are completed or refunded, keeping ticket entitlements in sync with transactions.

Example prompt: POST `/tickets/enable_addon` with ticket_id and addon_id when an upsell is purchased. POST `/tickets/disable_addon` if the addon is refunded or canceled.

### AI Agent for Event Operations

Let an AI agent handle Oveit event admin tasks - checking in attendees, pairing RFID wristbands, exporting attendee lists, and managing addons. Through Jentic, the agent searches by intent ('check in an Oveit ticket') and loads only the required endpoints. Session tokens are injected at execution time, keeping credentials out of agent context.

Example prompt: Use the Jentic search query 'check in an Oveit ticket' to find POST `/tickets/checkin`, load its schema, and execute with ticket_id provided by the user.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/seller/login` | Authenticate seller and retrieve session token |
| GET | `/seller/events` | List all events for a seller |
| GET | `/events/attendees` | Retrieve attendees for an event |
| POST | `/tickets/scan` | Scan and validate a ticket |
| POST | `/tickets/checkin` | Check in an attendee |
| POST | `/rfid/pair` | Pair an RFID tag with a ticket |
| POST | `/tickets/import` | Import tickets in bulk |

## Key resources

- **Events** — Event records with dates, venues, and ticket configurations
- **Attendees** — Registered attendees with contact details, ticket types, and check-in status
- **Tickets** — Individual ticket records tied to attendees and events
- **RFID Pairings** — Associations between RFID tags (wristbands, badges) and tickets for contactless access
- **Addons** — Ticket extras or upsells (merchandise, VIP upgrades, meals)

## Why Jentic

- **Setup:** Wiring Oveit by hand means logging in through `/seller/login` to get a bearer token and carrying it on every ticketing, check-in, and RFID call yourself. Through Jentic you install once, import the Oveit API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Oveit identifies events and tickets in the request body rather than the URL path, so scope the agent to the operations it needs, such as listing events, scanning tickets, or checking in attendees. Because you choose the allowed operations, actions like importing tickets or pairing RFID wristbands are not included unless you add them.
- **Credential handling:** Your Oveit session token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check in an Oveit ticket' or 'pair an RFID wristband', and Jentic returns the matching Oveit operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Ticketmaster API** — Ticketmaster handles large-scale ticketing for concerts, sports, and major events.
- **Ticketbud API** — Ticketbud API is an event ticketing and registration platform, offering an alternative to Oveit for selling tickets and managing attendees.

## FAQ

### What authentication does the Oveit API use?

The API uses session-based authentication. POST `/seller/login` with email and password returns a session token for subsequent requests. Through Jentic, session tokens are managed and refreshed automatically, keeping credentials out of agent context.

### Can I check in attendees programmatically?

Yes. POST `/tickets/checkin` marks a ticket as checked in. Use POST `/tickets/scan` first to validate the ticket before check-in.

### How do I pair RFID wristbands with tickets?

POST `/rfid/pair` with ticket_id and RFID tag ID associates the RFID device with the ticket, enabling contactless access control at event entrances or zones.

### Can I import tickets in bulk?

Yes. POST `/tickets/import` accepts an array of ticket data (name, email, ticket type) to create multiple attendee records at once, useful for migrations or corporate events.

### Is the Oveit API free?

API access is included with Oveit subscriptions. Pricing is based on event size, ticket volume, and plan tier, not API request count.

### How do I export attendee data for post-event analysis?

GET `/events/attendees` retrieves attendee records, and GET `/attendees/download_file` exports attendee data in bulk for CRM sync or analytics.

### Can I limit what my agent is allowed to do with the Oveit API?

Yes. Because Jentic One is self-hosted, your own rules decide which Oveit operations and credentials the agent can use, so you can allow read-only actions like GET `/seller/events` and GET `/events/attendees` while restricting anything that changes state. Since Oveit identifies events and tickets in the request body rather than the URL path, you scope by operation: you might permit POST `/tickets/scan` and POST `/tickets/checkin` for entrance staff but withhold POST `/tickets/import` or POST `/rfid/pair.` Operations you do not add are simply not available to the agent, and your stored session token is injected only for the calls you approve.