The API is scoped to one Business Unit. An API key is generated inside a Business Unit and can only read and write that unit’s events — never another unit’s, never another organization’s. See API keys.
What you can do
Automations fire for API actions exactly as they do for console actions: a registration created over the API triggers your “attendee added” automation, an approval triggers the confirmation flow, an arrival check-in triggers the welcome flow.
Base URL and interactive docs
Every endpoint in these pages lives under/v1 on your Orriven API host. In the examples we write the host as $BASE:
GET $BASE/openapi.json returns the full OpenAPI 3.1 specification (use it to generate a client in your language), and $BASE/docs serves an interactive reference where you can try every endpoint with your key.
Requests and responses
- Requests and responses are JSON; send
Content-Type: application/jsonon writes. - Timestamps travel as ISO 8601 with an offset (
2026-09-01T09:00:00+08:00). - Money is an integer in minor units of the event’s currency (¥120.00 →
12000), tax-inclusive — the same convention as the console. - Every request carries your key:
Authorization: Bearer <secret>. - The API is date-versioned: your key is pinned at creation, and every response echoes the effective version in the
Orriven-Versionheader.
Where to go next
API keys
Generate a key in the console — the secret shows exactly once.
Quickstart
Event → ticket type → registration → check-in, in seven curl calls.
Endpoint reference
Every resource, method and status code.
Ticket types
The console-side concepts the API mirrors.