Pretix

Pretix is an open-source event ticketing and registration platform used by organizers to sell tickets, manage attendees, and run box-office operations. The Pretix REST API exposes organizers, events, orders, tickets, vouchers, check-in lists, and related resources, allowing you to extract ticketing and attendee data for reporting and analytics. This connector reads data from the Pretix API into Nexla.

Power end-to-end data operations for your Pretix API with Nexla. Our bi-directional Pretix connector is purpose-built for Pretix, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Pretix or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Pretix workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Pretix credential, you need an API token from your Pretix account. Pretix uses team-scoped API tokens for authentication, and the token is sent in the Authorization header with a Token prefix (for example, Authorization: Token <your-token>).

To obtain a Pretix API token, follow these steps:

1. Sign in to your Pretix account. This connector's default endpoints target the hosted service at https://pretix.eu.

2. Open the settings for the organizer whose data you want to access, and navigate to the Teams section.

3. Select an existing team or create a new one, and ensure the team has the permissions required for the resources you plan to ingest (for example, permissions to view orders, vouchers, or organizer-level data).

4. In the team's settings, create a new API token by providing a name for it.

5. Copy the generated token immediately and store it securely, as it grants access to the resources permitted for that team and may not be shown again.

You will also need the organizer slug for most endpoints, and both the organizer slug and event slug for event-scoped endpoints. These slugs are the short identifiers that appear in your Pretix URLs. For more detail on authentication and available resources, see the Pretix REST API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Token	Yes	Yes	Pretix API token. Sent as 'Authorization: Token <token>'.

Create a credential in Nexla

1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Pretix API token in the API Token field. This token is sent in the Authorization header with the Token prefix on every request to the Pretix API and must be kept confidential.

   If your API token is compromised, revoke it in your Pretix team settings and generate a new one. The token grants access to the resources permitted for the team it belongs to and should be treated as sensitive information.

   For detailed information about authentication, permissions, and available resources, see the Pretix REST API documentation.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Pretix connector tile, then select the credential that will be used to connect to Pretix, and click Next; or, create a new Pretix credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Pretix endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Endpoints that operate within an organizer require the organizer slug, and event-scoped endpoints require both the organizer slug and the event slug. Provide these values when configuring the endpoint.

[Rest API] List Orgainzers

Retrieve organizers. This endpoint returns the organizers accessible to your API token. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Events

Retrieve events. This endpoint returns the events for a given organizer. Provide the organizer slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Customers

Retrieve customers. This endpoint returns the customers for a given organizer. Provide the organizer slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Sales Channels

Retrieve sales channels. This endpoint returns the sales channels configured for a given organizer. Provide the organizer slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Membership Types

Retrieve membership types. This endpoint returns the membership types defined for a given organizer. Provide the organizer slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Memberships

Retrieve memberships. This endpoint returns the memberships for a given organizer. Provide the organizer slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Giftcards

Retrieve giftcards. This endpoint returns the gift cards issued for a given organizer. Provide the organizer slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Reusable Media

Retrieve reusable media. This endpoint returns the reusable media records for a given organizer. Provide the organizer slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Teams

Retrieve teams. This endpoint returns the teams defined for a given organizer. Provide the organizer slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Devices

Retrieve devices. This endpoint returns the devices registered for a given organizer. Provide the organizer slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Webhooks

Retrieve webhooks. This endpoint returns the webhooks configured for a given organizer. Provide the organizer slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Tax Rules

Retrieve tax rules. This endpoint returns the tax rules defined for a specific event. Provide the organizer slug and the event slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Categories

Retrieve categories. This endpoint returns the product categories defined for a specific event. Provide the organizer slug and the event slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Items

Retrieve items. This endpoint returns the products (items) defined for a specific event. Provide the organizer slug and the event slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Orders

Retrieve orders. This endpoint returns the orders placed for a specific event. Provide the organizer slug and the event slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Vouchers

Retrieve vouchers. This endpoint returns the vouchers created for a specific event. Provide the organizer slug and the event slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Discounts

Retrieve discounts. This endpoint returns the discounts configured for a specific event. Provide the organizer slug and the event slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Checkin Lists

Retrieve check-in lists. This endpoint returns the check-in lists defined for a specific event. Provide the organizer slug and the event slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Waiting List Entries

Retrieve waiting list entries. This endpoint returns the waiting list entries for a specific event. Provide the organizer slug and the event slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

[Rest API] List Exporters

Retrieve exporters. This endpoint returns the exporters available for a specific event. Provide the organizer slug and the event slug to scope the request. Results are paginated, and Nexla automatically follows the pagination to fetch all available records.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Pretix data sources can also be manually configured to ingest data from any valid Pretix API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Pretix data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.