Alloovium

Developer Documentation

Build on Alloovium

Public REST API v2 and Model Context Protocol server for document intelligence. Everything you need to integrate Alloovium's vault, chat, workflows, and template filler into your own product or LLM agent.

Base URL

All production API v2 endpoints are served under Base URL. A separate staging environment is available for pre-production validation; use the staging base URL listed in the live OpenAPI servers block or provided with your staging credentials. Every request must be HTTPS.

Developer Console

Create test and live API keys, register OAuth clients, and monitor your monthly developer-credit allowance from path. Free and trial workspaces start with sandbox credits so you can validate integrations before moving into paid traffic.

Get started

Core concepts

Capabilities

Use cases

How it fits together

Alloovium's public surface is built on a capability registry. Every operation is declared once and automatically mounted as:

  • A REST endpoint with OpenAPI 3.1 schema, rate limiting, and scope enforcement.
  • An MCP tool with the same input/output schema for LLM agents.
  • An audit log entry tagged with the capability name for every call.

The OpenAPI spec at path is the canonical machine-readable reference. The Scalar-powered browser at /developers/api-reference lets you try every endpoint interactively.

Versioning and stability

The public API is v2. We commit to the following stability contract:

  • Error code fields are stable — we will never silently rename one.
  • Breaking changes ship behind a new version prefix, never inside v2.
  • Additive changes (new optional fields, new capabilities) may land at any time.
  • Deprecated endpoints run for at least 90 days with a header header.

Watch the changelog for additions and deprecations.

Get help

Contact email with your field (returned in every error response) and we can trace any call end-to-end. For security reports, email security.