canonical: https://jentic.com/apis/ticketco.no/ticketco-no

# Ticketco No TicketCo API

TicketCo is an event ticketing platform. This API provides programmatic access to manage events, tickets, and orders. Note: This specification is based on limited public documentation and may be incomplete. The API exposes 8 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create an event, list events. Covers 8 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Create an event
- List events
- Get an event
- Update an event
- Monitor TicketCo API operational status and events

## Use cases

### CRM Operations

Use the TicketCo API to perform crm operations programmatically. The API provides 8 endpoints covering core functionality including create an event, list events, get an event.

Example prompt: Call POST /events to create an event

### Automated events Management

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

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

### AI Agent Integration via Jentic

AI agents discover and call TicketCo 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 apiKey tokens manually.

Example prompt: Search Jentic for 'create an event', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/events` | Create an event |
| GET | `/events` | List events |
| GET | `/events/{eventId}` | Get an event |
| PUT | `/events/{eventId}` | Update an event |
| GET | `/events/{eventId}/tickets` | List tickets for an event |
| GET | `/tickets/{ticketId}` | Get a ticket |
| GET | `/orders` | List orders |
| GET | `/orders/{orderId}` | Get an order |

## Key resources

- **events** — Operations related to events
- **orders** — Operations related to orders
- **tickets** — Operations related to tickets

## Why Jentic

- **Setup:** Wiring the TicketCo API by hand means setting up its X-API-Key header, targeting the ticketco.events host, and building the event, ticket, and order calls yourself. Through Jentic you install once, import the TicketCo API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** TicketCo puts the event id in the URL path (`/events/{eventId}`, `/events/{eventId}/tickets`), so a rule can pin your agent to one event: it can read that event and its tickets and nothing else. You choose the operations it may call, so a change like creating or updating an event is not included unless you add it.
- **Credential handling:** Your TicketCo API key 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 'create an event' or 'look up an order', and Jentic returns the matching TicketCo API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the TicketCo API use?

The TicketCo API uses an API key passed in the `X-API-Key` header. 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 create an event with the TicketCo API?

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

### What are the rate limits for the TicketCo 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 create an event through Jentic?

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

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

The TicketCo API exposes 8 endpoints covering events, orders, tickets operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which TicketCo operations and credentials the agent may use. Since TicketCo puts the event id in the URL path (`/events/{eventId}` and `/events/{eventId}/tickets`), you can pin the agent to a single event so it only reads that event and its tickets. You also choose which operations it may call, so write actions like creating or updating an event (POST /events, PUT `/events/{eventId}`) stay off limits unless you add them.