canonical: https://jentic.com/apis/pims.io/pims-api

# Pims

Jentic publishes the only available OpenAPI specification for Pims API, keeping it validated and agent-ready. This Pims API variant provides event ticketing and facility management operations including event scheduling, ticket sales tracking, capacity management, category organization, and multi-channel distribution across 28 endpoints. It serves venue operators and event promoters who need programmatic control over ticketing operations.

## For AI agents

Manage event ticketing and facility operations including events, capacities, categories, channels, ticket counts, and promotions for venue and event management businesses.

## Scope

Does not handle payment processing, customer accounts, or venue booking - use for event ticketing operations and sales tracking only.

## Capabilities

- Track ticket sales counts with detailed per-event breakdowns
- Manage event capacities and seating allocations across venues
- Organize events into categories for catalog navigation
- Configure sales channels for multi-platform ticket distribution
- Create and manage promotional campaigns for events
- Monitor real-time ticket availability and sales velocity

## Use cases

### Event Ticket Sales Monitoring

Track real-time ticket sales for events through the Pims API. The `/events/{event_id}/ticket-counts` and `/events/{event_id}/ticket-counts/detailed` endpoints return current sales figures broken down by category and channel, enabling promoters to monitor demand and adjust marketing spend.

Example prompt: Retrieve detailed ticket counts for event ID 5001 broken down by category and channel

### Venue Capacity and Facility Management

Manage seating allocations and facility capacities for events. The API handles capacity configuration per event with category-level granularity, allowing venues to set limits by section and track remaining availability. Facility operators use this to coordinate room assignments, equipment allocation, and space utilization.

Example prompt: List all capacities for event ID 5001 and identify sections with less than 20% remaining availability

### Multi-Channel Ticket Distribution

Configure and manage sales channels through which tickets are distributed. The Pims API supports multiple distribution channels per event, enabling promoters to track which platforms generate the most sales and adjust allocation accordingly.

Example prompt: List all channels for event ID 5001 and retrieve ticket counts per channel

### AI Agent Event Operations

AI agents use the Pims API through Jentic to monitor ticket sales and manage event configurations without manual API setup. Agents search for ticketing operations by intent, load the endpoint schema, and execute calls with Jentic handling Basic authentication.

Example prompt: Search Jentic for 'monitor event ticket sales', load the Pims ticket-counts endpoint schema, and retrieve current sales figures

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/events` | List all events |
| GET | `/events/{event_id}` | Retrieve a specific event |
| GET | `/events/{event_id}/capacities` | List capacities for an event |
| GET | `/events/{event_id}/ticket-counts` | Get ticket sales counts |
| GET | `/events/{event_id}/ticket-counts/detailed` | Get detailed ticket count breakdown |
| GET | `/events/{event_id}/channels` | List sales channels for an event |
| GET | `/events/{event_id}/promotions` | List promotions for an event |
| GET | `/categories` | List all event categories |

## Key resources

- **Events** — Create and manage events with scheduling and configuration
- **Capacities** — Set and track venue capacity allocations per event
- **Categories** — Organize events and ticket types into categories
- **Channels** — Configure sales and distribution channels
- **Ticket Counts** — Retrieve ticket sales figures with detailed breakdowns
- **Promotions** — Manage promotional campaigns for events

## Why Jentic

- **Setup:** Wiring the Pims API by hand means setting up its basic auth, picking the right customer host from the demo or production servers, and coding each event, capacity, and ticket-count read yourself. Through Jentic you install once, import Pims from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Pims puts the event id in the URL path (`/events/{event_id}/...`), so a rule can pin your agent to one event: it can read that event's capacities, ticket counts, and channels. The operations exposed here are all reads, so you grant sales monitoring without any write, and you choose which of those reads the agent may call.
- **Credential handling:** Your Pims basic auth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'monitor event ticket sales' or 'check an event's remaining capacity', and Jentic returns the matching Pims operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Pims** — Same Pims ticketing platform accessed through the main API slug
- **Pims** — Same Pims ticketing platform accessed through the pims API slug
- **SeatGeek API** — SeatGeek provides ticket marketplace and event discovery for consumers while Pims handles venue-side operations

## FAQ

### Why is there no official OpenAPI spec for Pims API?

Pims does not publish an OpenAPI specification for this API variant. Jentic generates and maintains this spec so that AI agents and developers can call Pims API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Pims API use?

The Pims API uses HTTP Basic authentication. Your credentials are sent as a Base64-encoded username:password pair in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected automatically.

### Can I track ticket sales in real time with the Pims API?

Yes. The `/events/{event_id}/ticket-counts` endpoint returns current sales figures, and `/events/{event_id}/ticket-counts/detailed` provides breakdowns by category and channel for granular monitoring.

### How does this API variant differ from the other Pims slugs?

The pims.io vendor has three API slug variants (main, pims, pims-api) that all expose the same 28 event ticketing endpoints. They originate from different source specifications but provide equivalent functionality for event, capacity, and ticket management.

### How do I monitor event ticket sales through the Pims API using Jentic?

Search Jentic for 'monitor event ticket sales', load the `/events/{event_id}/ticket-counts` operation schema, and execute with your event ID. Jentic handles Basic auth injection and returns current ticket sales data with category breakdowns.

### Can I manage promotional campaigns for events?

Yes. The `/events/{event_id}/promotions` endpoint lists all active promotional campaigns for a specific event. Promotions can be configured to offer discounts, early-bird pricing, or special access across different sales channels.

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

Yes. Because you run Jentic One yourself, your own rules decide which Pims operations and credentials the agent may use. Pims puts the event id in the URL path, so you can pin the agent to a single event and let it read only that event's capacities, ticket counts, and channels. Every operation exposed here is a read, so you grant sales and capacity monitoring without any write access, and you choose exactly which of those reads the agent may call.