frequentix
Developers

An API-first platform, built to integrate.

frequentix is an API-only platform at its core — the storefront, console and scanner are all just clients of it. Bring the same surface to your own systems with OAuth clients, webhooks and a documented API.

Integrate

Connect frequentix to your stack

Read your events and orders over OAuth, react to real-time events with signed webhooks, and build from documentation whose worked examples are verified by the test suite.

OAuth API clients

Create machine-to-machine OAuth clients to integrate frequentix with your own systems — scoped reads over events, orders, tickets, contacts and entry scans (registration answers included), plus the writes automations need: upserting contacts, checking tickets in, and managing webhook subscriptions. Every list syncs incrementally: ask for what changed since your last pointer, deletions and erasures included.

Outbound webhooks

Subscribe to real-time events across the whole lifecycle — orders, tickets, check-ins, transfers, resale, waitlists, sessions, leads. Deliveries are HMAC-signed, retried with exponential backoff, logged, and auto-disabled with a reason if an endpoint keeps failing. Subscribe in the console, or by API — the REST-hook model automation platforms like Zapier use.

Built for retries

Every write on the integration surface takes an idempotency key, and every webhook delivery carries a stable delivery reference — so retries never double-write, double-charge or double-process.

Developer documentation

Every endpoint and webhook event is publicly documented — field-level schemas, worked payload examples, and signature-verification code in four languages. No account required.

Webhook events

Subscribe to what matters

19 events cover orders, tickets, add-ons, payments, waitlists and sessions. Scope a subscription to a single event or receive everything across an organiser. Deliveries are HMAC-signed, retried with backoff, logged, and auto-disabled with a reason if an endpoint keeps failing.

Explore the event catalogue →

Security & privacy

Attendee data protected end to end

Security is built into the data model, not layered on top — from per-event ticket encryption to a split authentication model with tightly scoped abilities and multi-factor sign-in for your team.

Encrypted ticket codes

Ticket QR codes are encrypted with a key unique to each event, so a scan reveals nothing without it. Each event’s key is itself encrypted at rest.

GDPR erasure

One action anonymises a contact, voids their tickets, invalidates their wallet passes and records the erasure in the audit log.

Audit logging & rate limiting

Actions that touch money, access, personal data or the setup of your events are recorded to an audit trail — who did it, when, and what changed — and every sensitive endpoint is throttled against abuse.

Split authentication

First-party staff and scanner tokens are kept separate from third-party OAuth clients, each with tightly scoped abilities and public identifiers that give nothing away.

Multi-factor authentication

Reaching anything sensitive — attendee data, exports, billing — requires a second factor: email one-time codes or an authenticator app, backed by single-use recovery codes and replay protection.

Sign in with Google

Your team can sign in with Google, so account access rides on Google’s own protections and second factor.

Start building

Create an organiser account, connect Stripe, and generate your first API client and webhook subscription.