Webhooks & the API
When a sale, a scan or a waitlist offer should reach your CRM, your finance system or your own site, frequentix can push it — or your systems can come and read it.
Webhooks

- Twelve event kinds can be pushed to an endpoint you nominate: orders created, refunded and cancelled, tickets scanned and updated, waitlist joins, offers and conversions, date cancellations, add-on redemptions and payment disputes. A subscription is organiser-wide or scoped to one event.
- Every delivery is signed, so your endpoint can prove it came from frequentix. The signing secret is shown once, at creation.
- A failing endpoint is retried eight times over about nine hours; if it never answers, the subscription disables itself and you get an email, so a silent outage can’t swallow a week of orders. A browsable delivery log shows every attempt and response.
The API
- API clients live in Settings → Integrations. Each carries scoped credentials — read access to events, orders, tickets and contacts, plus recording scans — and can be limited to named events. Narrowing a client’s scope applies immediately, even to tokens already issued.
- Like webhook secrets, a client secret is shown once. Lost one? Revoke and create a replacement — nothing can ever read it back.
For your developers
This article is the organiser’s view. Payload formats, signature verification, authentication and code samples live in the developer documentation — hand your developer that link and the two secrets, and they have everything they need.
