The ONCORR API lets your systems read events, registrations, check-ins, flight status and reports, create registrations and invitations, and receive webhooks the moment something happens. The same permissions power the AI tools (MCP) and the Zapier, Make and Office packages.
1. Get a key
Create a sandbox key (demo events only) or ask your ONCORR administrator for an API token.
2. Make a call
Send the key as a Bearer token. Start with GET /me.
3. Go live
Use a real token with only the scopes you need, and subscribe to webhooks.
Base URL
https://oncorr.info/api/v1
Your first call
curl https://oncorr.info/api/v1/me \
-H "Authorization: Bearer onc_your_token_here" \
-H "Accept: application/json"
The answer names the token, its owner, its scopes, its rate limit and whether it is a sandbox key. Then list the events the token can see:
curl "https://oncorr.info/api/v1/events?per_page=5&sort=start_date&direction=desc" -H "Authorization: Bearer onc_your_token_here"
Where tokens come from
- Sandbox key — any signed-in Summit staff member or organizer, on the Sandbox page. Works for 30 days on demo events only.
- API token — Summit staff: System → Integrations → API & webhooks. Organizers: Account → Integrations → API & webhooks (only their own events).
- OAuth 2.1 — for apps that sign people in themselves (AI connectors, the Outlook add-in). See Authentication.
Good to know
- Every list is paginated (
page,per_pageup to 100) and returnsdata,metaandlinks. - Card numbers, passport data and frequent-flyer numbers are never returned.
- Errors always look like
{"error": {"code": "…", "message": "…"}}— see Rate limits & errors. - The machine-readable description is at https://oncorr.info/api/docs/openapi.json (OpenAPI 3).