Skip to main content
RecordEngine exposes a REST API that gives you programmatic access to everything the UI can do — uploading documents, querying extracted data, updating statuses, managing contacts and folders, and triggering AI chat. Combined with the outbound webhook system, the API is the foundation for all RecordEngine integrations. RecordEngine Swagger UI at /api/docs

Base URL

All API endpoints are available at:
https://YOUR-INSTANCE/api/
For example, if your RecordEngine server is at https://a9f3d7e2.recordengine.ai, the API base URL is:
https://a9f3d7e2.recordengine.ai/api/
For local installations, the base URL is:
http://localhost:8510/

Interactive Documentation

RecordEngine includes a full Swagger UI at /api/docs:
https://YOUR-INSTANCE/api/docs
The Swagger UI lets you browse all available endpoints, see request and response schemas, and make live API calls directly from your browser using your Bearer token.
The Swagger UI is the fastest way to explore the API and test calls without writing any code. Use it to find the exact field names and response formats before building your integration.

Response Format

All API responses are JSON. A successful response returns an HTTP 200 status code with a JSON body. Errors return an appropriate HTTP error code with a detail message:
// Success
{
  "id": 847,
  "filename": "acme-invoice.pdf",
  "status": "Needs Review",
  "confidence_score": 87
}

// Error
{
  "detail": "Document not found"
}

HTTP Status Codes

CodeMeaning
200Success
201Created successfully
400Bad request — check your request body
401Unauthorised — missing or invalid Bearer token
403Forbidden — valid token but insufficient permissions
404Resource not found
422Unprocessable entity — request body failed validation
500Server error — check container logs

Rate Limits

The RecordEngine API has no enforced rate limits by default for on-premise deployments. Document processing throughput is governed by your hardware — specifically GPU VRAM and processing queue depth — rather than by API rate limiting.

API and Webhooks Together

The API and outbound webhooks are designed to work together:
  • Inbound (API): Your systems push documents and data into RecordEngine
  • Outbound (Webhooks): RecordEngine pushes processed results out to your systems
A typical integration uses both:
Your system  →  POST /api/documents/upload  →  RecordEngine
RecordEngine →  Webhook POST to your URL   →  Your system
See Outbound Webhooks for the full webhook payload schemas.

Available Endpoint Groups

GroupWhat it covers
DocumentsUpload, list, retrieve, update status, manage extracted fields
Contacts & FoldersCreate and list contacts and folders
CRM CorrelationPass and retrieve external_refs for CRM record linking
Deep-LinksGenerate direct URLs to open specific documents in the UI
WebhooksOutbound webhook configuration and payload schemas
Chat APIAsk questions across documents programmatically

OpenAPI Schema

The full OpenAPI 3.0 schema is available at:
https://YOUR-INSTANCE/api/openapi.json
You can import this into Postman, Insomnia, or any other API client:
  • Postman: File → Import → Link → paste the URL above
  • Insomnia: Application → Import → From URL → paste the URL above
See OpenAPI / Swagger for more details.