Pims

Name: Pims API
Brand: Pims API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder Managementbasic28 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Pims to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pims, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Pims API.

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

GET STARTED

Start building with Pims API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Pims API for, with concrete tasks.

★ 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.

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.

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.

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.

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

Key Endpoints

28 endpoints — jentic publishes the only available openapi specification for pims api, keeping it validated and agent-ready.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Pims Basic auth credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens so raw passwords never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'monitor event ticket sales') and Jentic returns matching Pims operations with their input schemas, so the agent can call the right endpoint without reading docs.

Time to first call

Direct Pims integration: 1-2 days for auth setup and endpoint discovery. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Pims

Same Pims ticketing platform accessed through the main API slug

This is the same Pims platform. The main slug is the primary entry point for the same event ticketing endpoints.

Alternative

Pims

Same Pims ticketing platform accessed through the pims API slug

This is the same Pims platform accessed through a different slug. All variants provide equivalent endpoint coverage.

Complementary

SeatGeek API

SeatGeek provides ticket marketplace and event discovery for consumers while Pims handles venue-side operations

Use SeatGeek when you need consumer-facing event discovery, ticket marketplace pricing, or secondary market data rather than venue-side operations.

FAQs

Specific to using Pims API through Jentic.

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 at https://app.jentic.com/sign-up.

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 the MAXsystem vault 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.