Skip to content

Design philosophy ​

Idempotency ​

In both directions, every call can be repeated with the same result. Your records reach us as upserts: an event or order we already have is updated, never duplicated, so overlapping reads and repeated webhooks are harmless. Our calls to you are upserts too: vouchers and webhooks carry our own ids, so a retry after a timeout never creates a second one, and a delete of something already gone still succeeds.

Write access ​

We only write when you advertise vouchers or managed webhooks, and then only to vouchers and webhooks we created ourselves. We never touch anything made in your back office.

Rate limits ​

You configure the rate limit: send config.rateLimit.requestsPerMinute in /v1/account and we stay below it, across all organisers who connected your platform together, as a steady stream rather than in bursts. Pages come in the size you choose, and every 429 is respected for as long as Retry-After asks.

Versioning ​

Records and capabilities get new properties over time, without a new version: we ignore what we don't know, and so can you. A change that would break an implementation, if one is ever needed, becomes a new version of that one capability, and everything else stays as it is. You choose when to migrate: switch the capability's version in /v1/account once you serve the new paths.