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.
Connect frequentix to your stack
Read your events and orders over OAuth, react to real-time events with signed webhooks, and rely on idempotency keys so retries never double-charge or double-import.
OAuth API clients
Create machine-to-machine OAuth clients to integrate frequentix with your own systems, reading events and orders scoped to the owning organiser.
Outbound webhooks
Subscribe to real-time events — order created, order refunded, order cancelled, ticket scanned, ticket updated, charge disputed. Deliveries are HMAC-signed, retried with exponential backoff, logged, and auto-disabled with a reason if an endpoint keeps failing.
Idempotency keys
Payment and import endpoints accept idempotency keys, so a retried request never double-charges or double-imports.
OpenAPI reference
An auto-generated, authenticated OpenAPI reference documents the whole versioned API surface for your developers.
Subscribe to what matters
Scope a subscription to a single event or receive everything across an organiser. Deliveries are HMAC-signed, retried with exponential backoff, logged, and auto-disabled with a reason if an endpoint keeps failing.
order.createdAn order was confirmed and tickets issued.order.refundedAn order was fully or partially refunded.order.cancelledAn order was cancelled and its tickets voided.ticket.scannedA ticket was scanned at an entry point.ticket.updatedA ticket was reassigned, voided or changed.charge.disputedA payment was disputed or charged back.
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
Access- and money-affecting actions are recorded to an audit trail, 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.