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.