Eriga for developers
Everything you need to build against Eriga — concepts, guides, and the REST API reference.
Start here
Section titled “Start here” Authentication OAuth2 access tokens, JWT validation, and the X-Space-Id tenant header.
Domain model The six aggregates exposed by the API, their fields, and invariants.
Permissions & roles Role model and the use-case matrix enforced by the API.
Errors Error response envelope and the exception-to-HTTP-status mapping.
What you can build
Section titled “What you can build” Model an organization Create Units to group Resources (people, equipment, environments, substances) by site, team, or cost center.
Define recurring obligations Declare Actions — trainings, medical checks, inspections — with a validity period and target Resource type.
Record fulfillment Issue Certificates linking a Resource to an Action, with expiry dates and attachments to external documents.
Query compliance state Computed on the fly — obligations, gaps, and expiring certificates across a Space, Unit, or Resource.
Conventions
Section titled “Conventions”- IDs are UUIDs.
- Timestamps are ISO 8601 with timezone.
- Pagination uses
pageandpageSizequery parameters; responses include atotalcount. - All requests require an
Authorization: Bearer <token>header; most also requireX-Space-Idto select the tenant. - Errors follow a consistent JSON body with an HTTP status derived from the exception class name — see Errors.