Table of contents¶
- User Guide
- Organizer accounts and teams
- Creating an event
- Configuring an event
- Product structure guide
- Terminology
- Use case: Multiple price levels
- Use case: Early-bird tiers based on dates
- Use case: Early-bird tiers based on ticket numbers
- Use case: Up-selling of ticket extras
- Use case: Conference with workshops
- Use case: Discounted packages
- Use case: Group discounts
- Use case: Restricted audience
- Use case: Time slots
- Use case: Season tickets
- Use case: Mixed taxation
- Embeddable Widget
- Example
- Styling
- SSL
- Always open a new tab
- Pre-selecting a voucher
- Disabling the voucher input
- Enabling the button-style single item select
- Filtering products
- Multi-event selection
- pretix Button
- Dynamically opening the widget
- Dynamically loading the widget
- Waiting for the widget to load or close
- Passing user data to the widget
- Offering wallet payments (Apple Pay, Google Pay) within the widget
- Content Security Policy
- External payment providers and Cross-Origin-Opener-Policy
- Working with Cross-Origin-Embedder-Policy
- Customer accounts
- Gift cards
- FAQ and Troubleshooting
- Markdown Guide
- Android version support policy
- Glossary
- Administrator documentation
- REST API
- Basic concepts
- Authentication
- Resources and endpoints
- Organizers
- Events
- Event series dates / Sub-events
- Tax rules
- Item categories
- Items
- Item variations
- Item bundles
- Item add-ons
- Item Meta Properties
- Questions
- Question options
- Quotas
- Orders
- Invoices
- Vouchers
- Discounts
- Check-in
- Check-in lists
- Waiting list entries
- Customers
- Sales channels
- Membership types
- Memberships
- Gift cards
- Reusable media
- Cart positions
- Teams
- Devices
- Webhooks
- Seating plans
- Data exporters
- Scheduled data exports
- Data shredders
- Scheduled email rules
- Auto check-in rules
- pretix Hosted billing invoices
- pretix Hosted reseller API
- Seats
- Rate limiting
- Webhooks
- API Usage Guides
- Developer documentation
- Concepts and Terminology
- Development setup
- Contributing to pretix
- Implementation and Utilities
- Algorithms
- Plugin development
- Creating a plugin
- Writing an exporter plugin
- Writing a ticket output plugin
- Writing a payment provider plugin
- Porting a payment provider from pretix 1.x to pretix 2.x
- Writing an HTML e-mail renderer plugin
- Writing a template placeholder plugin
- Writing an invoice renderer plugin
- Writing a data shredder
- Extending the import process
- Creating custom views
- Handling cookie consent
- Pluggable authentication backends
- General APIs
- Plugin quality checklist
- Directory structure
- Translating pretix
- NFC media
- Plugin documentation
- License FAQ
- How is pretix licensed?
- How can it be AGPL if there are additional terms?
- Why did you choose this license model?
- What do I need to do if I use pretix unmodified?
- What do I need to do if I modify pretix?
- Does the AGPL copyleft mechanism extend to plugins?
- Can I create proprietary or secret plugins?
- What licenses can plugins use?
- What do I need to do if I want to contribute my changes back?
- What if I want to re-use a minor part of pretix in my project?
- What can I use the name “pretix” for?