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

# Ticketbud API

The Ticketbud API allows you to access event and ticket data from Ticketbud. Authenticate using OAuth 2.0 to access events, tickets, check-in functionality, and sales data. The API exposes 9 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically get current user, list events. Covers 9 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Get current user
- List events
- Check in a ticket
- Query and filter Ticketbud API records by parameters
- Monitor Ticketbud API operational status and events

## Use cases

### Identity and Authentication Operations

Use the Ticketbud API to perform identity auth operations programmatically. The API provides 9 endpoints covering core functionality including get current user, list events, get a single event.

Example prompt: Call GET /me.json to get current user

### Automated User Management

Automate user operations by combining multiple Ticketbud API endpoints. Agents can list events and then get a single event in a single workflow.

Example prompt: Call GET /events.json to list events, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Ticketbud API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'get current user', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/me.json` | Get current user |
| GET | `/events.json` | List events |
| GET | `/events/{id}.json` | Get a single event |
| GET | `/events/{id}/totals.json` | Get event totals |
| GET | `/events/{event_id}/tickets.json` | List tickets for an event |
| GET | `/events/{event_id}/tickets/{id}.json` | Get a single ticket |
| PUT | `/events/{event_id}/tickets/{id}/check_in.json` | Check in a ticket |
| GET | `/events/{event_id}/ticket_sales` | Get ticket sales |

## Key resources

- **User** — User account operations
- **Events** — Event management
- **Tickets** — Ticket management and check-in

## Why Jentic

- **Setup:** Wiring the Ticketbud API by hand means running its OAuth2 authorization-code flow, holding the access token, and building the event and ticket calls yourself. Through Jentic you install once, import the Ticketbud API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Ticketbud puts the event and ticket ids in the URL path (`/events/{event_id}/tickets/{id}`), so a rule can pin your agent to one event: it can read that event, its totals, and its tickets and nothing else. You choose the operations it may call, so a state change like checking in a ticket is not included unless you add it.
- **Credential handling:** Your Ticketbud 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 'list my events' or 'check in a ticket', and Jentic returns the matching Ticketbud API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Ticketbud API use?

The Ticketbud API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get current user with the Ticketbud API?

Yes. Use the GET /me.json endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Ticketbud API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get current user through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get current user'. Jentic returns the matching Ticketbud API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Ticketbud API have?

The Ticketbud API exposes 9 endpoints covering user, events, tickets operations.

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

Yes. Ticketbud puts the event and ticket ids in the URL path, so a rule in your self-hosted Jentic One instance can pin your agent to a single event, letting it read that event, its totals, and its tickets and nothing else. You decide which operations the agent may call, so a state-changing action like the PUT check-in on a ticket is excluded unless you explicitly add it. Because Jentic One is run by you, your own rules and stored credentials govern every call the agent makes.