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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpretix.eu%2Fpretix" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpretix.eu%2Fpretix" | 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

Manage individual order positions including attendee details and ticket types

Approve or deny orders pending manual review in controlled-access events

GET STARTED

Start building with pretix API

Explore with Jentic One

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

POST

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

Clone an event with all settings

POST

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

Approve a pending order

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the pretix API by hand means formatting your token into the 'Token <value>' Authorization header against pretix.eu/api/v1 and threading organizer and event ids through every hierarchical path yourself. Through Jentic you install once, import the pretix API from the API Directory, store the token once, and your agent calls it.

Permission scoping

pretix puts the organizer and event ids in the URL path (/organizers/{organizer}/events/{event}/...), so a rule can pin your agent to one event: it can read and create that event's orders and nothing else. You choose the operations it may call, so marking an order paid, cancelling one, or cloning the event is not included unless you add it.

Credential isolation

Your pretix API token 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.

Intent-based discovery

Agents search Jentic by intent such as 'list ticket orders for an event' or 'create an order', and Jentic returns the matching pretix operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 your Jentic One instance 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.

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

Yes. Because pretix carries the organizer and event ids in the URL path (/organizers/{organizer}/events/{event}/...), the rules you set in your self-hosted Jentic One instance can pin the agent to a single event so it reads and creates only that event's orders and nothing else. You also decide which operations it may call, so marking an order paid, cancelling one, or cloning the event stays off-limits unless you explicitly allow it. Only the operations and credentials you grant are ever available to the agent.

pretix API

Name: pretix API
Brand: pretix API
Availability: InStock

AI ReadinessFoundational (C+)58/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceOrder ManagementapiKey27 EndpointsREST

For Agents

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

Use for: I need to create a new ticketing event, I want to list all orders for a specific event, Mark an order as paid after receiving bank transfer confirmation, Check the details of a specific order by its code

Not supported: Does not handle venue management, seating charts, or marketing campaigns - use for event ticketing and order management only.

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. It supports the complete event lifecycle from creation and cloning through ticket sales, payment handling, order approval workflows, and position-level management. The API uses a hierarchical resource model where organizers own events, events contain orders, and orders contain individual ticket positions.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C-Signals: 4

87%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

25%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

23%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

61%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C+Signals: 1

59%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the pretix API to your agent

Capabilities

Start building with pretix API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

pretix API

Jentic AI Readiness Score

pretix API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness