pretix API

Name: pretix API
Brand: pretix API
Availability: InStock

✓ Official Vendor SpecE CommerceOrder ManagementapiKey27 EndpointsREST

For Agents

Manage event ticketing through pretix — create events, process orders, handle payments and cancellations, and track attendee positions.

Install Jentic One Beta

Connect the pretix API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the pretix API, 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 pretix API.

Create and configure ticketing events with custom settings under organizer accounts

Process ticket orders with payment tracking, approval workflows, and deadline extensions

Clone existing events to quickly replicate configurations for recurring series

GET STARTED

Start building with pretix API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use pretix API for, with concrete tasks.

★ Event Ticketing Operations

Manage the full lifecycle of event ticket sales from creating events through processing orders and tracking attendees. The pretix API enables automated event setup with configurable pricing, capacity limits, and payment options. Orders flow through defined states (pending, paid, canceled) with API controls for each transition. This powers box office systems, embedded ticket widgets, and third-party sales channels that need direct access to the ticketing backend.

Create a new event under an organizer via POST /organizers/{organizer}/events/, then list its orders via GET /organizers/{organizer}/events/{event}/orders/ to confirm the event is active

Order Payment and Approval Workflows

Handle order payment confirmations, manual approval processes, and deadline management for events that use bank transfer or invoice payment methods. The pretix API provides dedicated endpoints to mark orders paid, approve or deny pending orders, extend payment deadlines, and cancel or reactivate orders. This supports finance teams processing offline payments and event managers who gate attendance behind manual approval.

Retrieve a pending order via GET /organizers/{organizer}/events/{event}/orders/{code}/, then mark it paid via POST /organizers/{organizer}/events/{event}/orders/{code}/mark_paid/

Recurring Event Series Management

Set up recurring events efficiently by cloning existing event configurations including products, quotas, questions, and payment settings. The clone endpoint creates a new event with all settings copied, requiring only date and name updates. This eliminates repetitive configuration for weekly meetups, monthly workshops, or annual conference series where the event structure stays consistent across dates.

Clone an existing event via POST /organizers/{organizer}/events/{event}/clone/ and update the new event's dates via PATCH /organizers/{organizer}/events/{event}/

AI Agent Ticketing Automation

AI agents use the pretix API through Jentic to automate ticketing operations including order monitoring, payment processing, and event management. The agent searches for ticketing operations, loads endpoint schemas with the hierarchical path structure (organizer/event/order), and executes multi-step workflows like checking pending orders and marking them paid without manual intervention.

Search Jentic for 'list pending ticket orders', load the orders operation schema, and execute to retrieve all orders with pending payment status for a specific event

Key Endpoints

27 endpoints — the pretix api provides full programmatic control over the pretix event ticketing platform, covering organizer management, event configuration, order processing, and attendee tracking across 27 endpoints.

METHOD

PATH

DESCRIPTION

POST

/organizers/{organizer}/events/

Create a new event

GET

/organizers/{organizer}/events/{event}/orders/

List all orders for an event

POST

/organizers/{organizer}/events/{event}/orders/

Create a new order

POST

/organizers/{organizer}/events/{event}/orders/{code}/mark_paid/

Mark order as paid

POST

/organizers/{organizer}/events/{event}/orders/{code}/mark_canceled/

Cancel an order

POST

/organizers/{organizer}/events/{event}/clone/

Clone an event with all settings

POST

/organizers/{organizer}/events/{event}/orders/{code}/approve/

Approve a pending order

GET

/organizers/{organizer}/events/{event}/orderpositions/

List order positions (attendees)

POST

/organizers/{organizer}/events/

Create a new event

GET

/organizers/{organizer}/events/{event}/orders/

List all orders for an event

POST

/organizers/{organizer}/events/{event}/orders/

Create a new order

POST

/organizers/{organizer}/events/{event}/orders/{code}/mark_paid/

Mark order as paid

POST

/organizers/{organizer}/events/{event}/orders/{code}/mark_canceled/

Cancel an order

Why Jentic?

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

Credential isolation

pretix API tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive requests with the 'Token <value>' Authorization header pre-configured, so raw tokens never enter agent context.

Intent-based discovery

Agents search by intent (e.g., 'list event ticket orders') and Jentic returns matching pretix operations with their hierarchical path schemas, including organizer and event path parameters.

Time to first call

Direct pretix integration: 2-3 days for auth, hierarchical path navigation, and order state machine handling. Through Jentic: under 1 hour — search for event or order operations, load schemas, and execute.

FAQs

Specific to using pretix API through Jentic.

What authentication does the pretix API use?

The pretix API uses token-based authentication with the format 'Token <your-token>' in the Authorization header. Through Jentic, your pretix token is stored encrypted in the MAXsystem vault and agents receive requests with the Authorization header pre-configured.

Can I mark an order as paid after receiving an offline payment?

Yes. Use POST /organizers/{organizer}/events/{event}/orders/{code}/mark_paid/ to transition an order from pending to paid status. This is designed for bank transfer and invoice payment methods where payment confirmation happens outside the platform.

What are the rate limits for the pretix API?

The pretix API applies rate limiting based on your account type. Self-hosted instances can configure limits freely. For pretix.eu hosted accounts, standard limits apply per authentication token. Monitor HTTP 429 responses and implement exponential backoff.

How do I create a new event and start selling tickets through Jentic?

Search Jentic for 'create ticketing event', load the events creation operation schema, and execute with organizer slug, event name, dates, and currency. The schema shows all required fields including the organizer path parameter. Install the SDK with pip install jentic to get started.

Can I clone an event to create a recurring series?

Yes. POST /organizers/{organizer}/events/{event}/clone/ creates a complete copy of an event including all products, quotas, questions, and settings. You then update the new event's dates and name via PATCH to differentiate it from the original.

How does the order approval workflow function?

Events can require manual order approval. Orders enter a pending-approval state, visible via GET /organizers/{organizer}/events/{event}/orders/. Use POST .../orders/{code}/approve/ to confirm or POST .../orders/{code}/deny/ to reject. Only approved orders proceed to payment.

pretix API

Connect the pretix API to your agent

Capabilities

Start building with pretix API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs