Developer APIs & OAuth Integration for Events

Build on Dreep

Dreep exposes native APIs and OAuth so you can integrate ticketing, payments, and attendee data into your own products and workflows.

What you can build

• OAuth 2.0 (with PKCE) sign-in with Dreep accounts
• Programmatic access to events, ticket types, and orders
• Cashless wallet and payment integrations
• Webhooks for tickets, payments, and check-ins

How integration works

Applications authenticate with OAuth 2.0 using PKCE, so an integration never handles a user's Dreep password. Access tokens are scoped, meaning an app that only needs to read events cannot also move money. Server-to-server integrations can use API keys instead, scoped the same way.

Events and orders

Read events, ticket types, availability, and orders programmatically - useful for syncing a festival lineup into your own site, mirroring inventory into a partner marketplace, or exporting attendance into a CRM.

Webhooks

Subscribe to ticket, payment, and check-in events so your systems react as things happen instead of polling. Deliveries are signed, so you can verify a payload genuinely came from Dreep before acting on it.

See how Dreep compares or explore use cases.