Developers
Build on eAviora
A versioned REST API, an MCP server for AI assistants, signed webhooks and enterprise sign-in, on the same permissions as the app.
REST API, version 1
Read and write your records
46 endpoints across records, links, actions, documents, evidence, imports, exports, webhooks and the audit log. The contract is generated from the running code, so the spec and the API cannot drift.
Keys
Created by an administrator in settings, scoped to one organisation.
References
A record has the same reference in the API as on screen.
Limits
Every response states your remaining calls in X-RateLimit headers.
Workflow
A record’s workflow stage moves in the app, by a person: the API cannot set it. A key with write scope can update an action’s status, so give write scope only to systems you trust.
Audit
Every write is logged under the key that made it, in the same transaction.
curl https://app.eaviora.com/api/v1/records?type=occurrence&limit=1 \
-H "Authorization: Bearer $EAVIORA_API_KEY"
{
"data": [{
"reference": "SMS-OCC-2026-0184",
"type": "occurrence",
"title": "Tug contact with aircraft at stand B14",
"stage": "investigation",
"riskLevel": "undesirable"
}],
"pagination": { "limit": 1, "offset": 0, "total": 1 }
}MCP server
Connect an AI assistant to your records
Add eAviora as a connector in an assistant that supports MCP. The person consents in the app, and the assistant acts with their role, never more.
Endpoint
/api/mcp/mcp
Sign-in
OAuth 2.1 with PKCE and dynamic registration. Access tokens last an hour; refresh tokens rotate over 30 days.
Consent
The person grants read, or read and write, and sees what they hand over.
Limits on writes
Writes go straight to the record within the person’s role, and are audited. An assistant cannot move a record’s workflow stage or a governance decision: a person does.
Read tools · 6
- list_modules
- search_records
- get_record
- get_record_links
- get_import_job
- list_export_jobs
Write tools · 5
- create_record
- update_record
- link_records
- start_csv_import
- request_export
11 tools in all
Webhooks
Signed events, with a delivery feed
Subscribe to record events and verify each one with the zero-dependency SDK, on Node, Deno, Bun, Cloudflare Workers or the browser.
Signature
HMAC-SHA256 over the timestamp and the body, checked in constant time.
Addresses
Checked against private and internal ranges when saved, and again before each send.
Secrets
Shown once when created, and rotated whenever you choose.
Failures
The delivery feed in settings replays one event, or every failed one. An endpoint that fails ten times in a row is paused.
Enterprise sign-in and data
What your security review will ask
Single sign-on
SAML 2.0 with Okta, Microsoft Entra or Google, just-in-time accounts, and sign-on enforced for your domain.
Provisioning
SCIM 2.0 creates and removes accounts, so a leaver loses access without a manual step.
Multi-factor
Multi-factor sign-in for every user. Passkeys are available as an experimental option.
Isolation
Row-level security in the database, under a role that cannot bypass it.
Export
Every record and the audit log, as JSON or CSV, at any time.