Developers and API
Acriva has a REST API that speaks JSON over HTTPS. The app itself uses the same API, so everything you do in the app will be possible from your own systems as well.
API reference
Section titled “API reference”The API reference lists every endpoint with its parameters, request bodies and responses. It is generated from the OpenAPI document of the current version, so it always matches what Acriva runs.
Every endpoint of a workspace starts with /api/v1/t/{tenant}/, where {tenant} is the address of
the workspace. Errors come back as problem details (RFC 9457) with a title in the language of the
request.
Connecting your systems
Section titled “Connecting your systems”- API keys: sign in from a server without a user.
- Upload API: send documents to Acriva.
- Webhooks: react when something happens in a workspace.
- Email ingestion: send documents by email.
Changes to the API
Section titled “Changes to the API”The API is versioned in its path (/api/v1/). What changes with each version is in the
changelog.