API overview
The Eriga REST API exposes the full domain — Spaces, Units, Resources, Actions, Certificates, Compliance — over JSON/HTTPS.
Base URL
Section titled “Base URL”https://api.eriga.appConventions
Section titled “Conventions”- IDs are UUIDs (
01J0...ULID-compatible) - Timestamps are ISO 8601 with timezone (
2026-05-04T10:00:00Z) - Pagination uses
pageandpageSizequery parameters; responses includetotal - All requests need
Authorization: Bearer <token> - Most endpoints need
X-Space-Idto select the tenant - Errors return a JSON envelope with HTTP status derived from the exception class — see Errors
OpenAPI specification
Section titled “OpenAPI specification”The API is fully described by an OpenAPI 3.1 spec, fetched live at:
https://api.eriga.app/api-docs-jsonThis spec drives the API Reference on this site and can be used to generate clients in any language.
What you can build
Section titled “What you can build”| Need | Operation |
|---|---|
| Model an organization | POST /units — create units to group resources by site, team, or any dimension |
| Define recurring obligations | POST /actions — declare trainings, medical checks, inspections with validity periods |
| Record fulfillment | POST /certificates — issue certificates linking resources to actions |
| Query compliance | GET /compliance/space — computed on the fly across Space, Unit, Resource |
SDKs and tooling
Section titled “SDKs and tooling”- OpenAPI spec — generate clients in any language from the JSON spec
- TypeScript / JavaScript SDK — coming soon
- Python SDK — coming soon
- MCP server — see user docs for AI agent integration
- Webhooks — see Webhooks
- Zapier — see Zapier
Get started
Section titled “Get started”- Authenticate — get an access token
- Browse the API Reference
- Check Errors and Domain model