canonical: https://jentic.com/apis/ticketsource.io/ticketsource

# TicketSource Zapier API

The TicketSource Zapier integration API for managing customers, events, and bookings. The API exposes 6 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically get customers, get events. Covers 6 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Get Customers
- Find Customer
- Create Customer
- Query and filter TicketSource Zapier API records by parameters
- Monitor TicketSource Zapier API operational status and events

## Use cases

### E-Commerce Operations

Use the TicketSource Zapier API to perform e commerce operations programmatically. The API provides 6 endpoints covering core functionality including get customers, get events, get bookings.

Example prompt: Call POST /customers to get customers

### Automated bookings Management

Automate bookings operations by combining multiple TicketSource Zapier API endpoints. Agents can get events and then get bookings in a single workflow.

Example prompt: Call POST /events to get events, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TicketSource Zapier 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 customers', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/customers` | Get Customers |
| POST | `/events` | Get Events |
| POST | `/bookings` | Get Bookings |
| POST | `/find-customer` | Find Customer |
| POST | `/find-event` | Find Event |
| POST | `/new-customer` | Create Customer |

## Key resources

- **bookings** — Operations related to bookings
- **customers** — Operations related to customers
- **events** — Operations related to events
- **find-customer** — Operations related to find-customer
- **find-event** — Operations related to find-event

## Why Jentic

- **Setup:** Wiring the TicketSource Zapier API by hand means running its OAuth2 authorization-code flow against the ticketsource.co.uk host, holding the token, and building the customer, event, and booking calls yourself. Through Jentic you install once, import the TicketSource Zapier API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** These operations take their target in the request body rather than a path id, so scoping is operations-only: you limit the agent to the operations it needs, such as finding a customer or creating a booking, rather than pinning it to one record. Any operation you leave out, such as creating a customer, is not available to the agent unless you add it.
- **Credential handling:** Your TicketSource 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 'find a customer' or 'create a booking', and Jentic returns the matching TicketSource Zapier API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the TicketSource Zapier API use?

The TicketSource Zapier 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 customers with the TicketSource Zapier API?

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

### What are the rate limits for the TicketSource Zapier 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 customers through Jentic?

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

### How many endpoints does the TicketSource Zapier API have?

The TicketSource Zapier API exposes 6 endpoints covering bookings, customers, events operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which TicketSource operations and credentials the agent may use. These operations take their target in the request body rather than a path id, so scoping is operations-only: you grant just the operations the agent needs, such as finding a customer or creating a booking, and leave out the rest, such as creating a customer. Any operation you do not add stays unavailable to the agent.