PassPassPassPass
DOCS
Documentation
Updates
Create event
Home
PassPassPassPass

The ticketing service for event organizers.

Discover PassPass Pro →

Documentation

Quick startAll themesAll articlesUpdates

Quick links

PassPass ProFrequently asked questionsOpen ticketContact us

Quick access

© 2024 PassPass. All rights reserved.
Mentions légalesPassPass - Event ticketing

Public API and Webhooks

Connect your tools (CRM, accounting, marketing, automations…) to PassPass using the REST API and real-time webhooks.

Last updated : August 7, 2026

PassPass offers a REST API and webhooks to connect your ticketing system to your external tools: CRM, accounting, marketing, automations.

Go to Settings > Developers to access these features.

For any technical questions or need for support, feel free to contact our support.

Contact support

Public API

The API allows you to read the data of your events, orders, and participants from an external system.

Connection Information

  • Base URL : https://api.passpass.be/api/public

  • Authentication : Authorization: Bearer <your-key>

  • Interactive Documentation (Swagger) : api.passpass.be/api/public/docs

  • Complete Technical Reference : Public API: Technical Reference

Create an API Key

  1. Go to Settings > Developers.

  2. Click on New API Key.

  3. Give a descriptive name to your key (e.g., "Sync CRM", "Export accounting").

  4. Check the necessary permissions.

  5. Copy the generated key and keep it in a safe place. The secret is displayed only once.

Available Permissions

Each key only has access to the data you authorize. All permissions are read-only.

  • Events (events:read) : title, description, dates, locations, tickets, gauges

  • Orders (orders:read) : buyer, purchased tickets, payment status, billing

  • Financial Orders (orders:read:financial) : service fees and net amount to be refunded

  • Order Form (orders:read:form_answers) : order form responses

  • Attendees (attendees:read) : identifier, assigned ticket, check-in status

  • Attendee Contact (attendees:read:contact) : first name, last name, and email

  • Financial Attendees (attendees:read:financial) : amount paid per attendee

  • Attendee Form (attendees:read:form_answers) : attendee form responses

  • Full Attendees (attendees:read:full) : access token to the ticket QR code (sensitive)

The contact, form_answers, and full extensions provide access to personal data. Only activate them if the recipient system is GDPR compliant.

Before connecting your system, test your calls with a tool like Postman. Paste the base URL, add your key in the Authorization header, and check that you receive the expected data.


Webhooks

Webhooks send a notification to a URL of your choice for each important event (payment received, ticket scanned...). Ideal for real-time reactions without continuously querying the API.

Complete Technical Reference: Webhooks: Technical Reference

Create an Endpoint

  1. Go to Settings > Developers.

  2. Click on New Webhook Endpoint.

  3. Enter your server's URL.

  4. Check the types of events to receive.

  5. Select the permissions to control the data included in the payload.

Available Events

  • order.created : order created

  • order.paid : order paid (includes finalized free orders)

  • order.cancelled : order cancelled

  • order.expired : order expired

  • ticket.validated : ticket validated at entry

  • event.published : event published

  • event.updated : event updated

Security and Reliability

Each notification is signed via the X-PassPass-Signature header. Your server should verify this signature to confirm that the request indeed comes from PassPass.

If your server does not respond, PassPass automatically retries with increasing delays (6 attempts). After 20 consecutive failures, the endpoint is disabled to prevent unnecessary sends.

Permissions work the same way as for the API: you control exactly what data is included in each notification.


Best Practices

  1. Only activate the necessary permissions. Less exposed data, less risk.

  2. Never share an API key publicly. Avoid placing it in a GitHub repository or accessible code. Use environment variables.

  3. Verify webhook signatures. Check the X-PassPass-Signature header for each received notification.

  4. Respond quickly to webhooks. Your endpoint should return an HTTP 200 without delay. If processing takes time, acknowledge receipt and process in the background.


Use Cases

Synchronize Attendees with a CRM

Use the API with the attendees:read and attendees:read:contact permissions, or set up a webhook on order.paid, to automatically send each new attendee to HubSpot, Brevo, Salesforce, or any other CRM.

Export Orders to Your Accounting

Use the API with the orders:read and orders:read:financial permissions to retrieve amounts, service fees, and payment statuses, and inject them into your accounting software.

No-code Automations with Zapier, Make, or n8n

Combine the API or webhooks with an automation tool to create workflows without coding. Some examples: add a Mailchimp contact for each sale, send a Slack notification when a ticket is scanned, feed a Google Sheet in real-time.

Related articles

3 articles in this category