Arkrel
Sign in
v1.0.0
OpenAPI 3.1.0

Document Extraction API

Email sign-up at /app/api/auth/sign-up/email requires an x-turnstile-token header in production. Failed or unavailable bot verification returns 403 with code BOT_CHECK_REQUIRED. Social sign-up is unaffected. Documents in. Verified data out.

The public REST API (v1) turns documents (invoices, receipts, purchase orders, bank statements, delivery notes, or custom schemas) into structured, verified data. Every document reaches an explicit terminal state. Every extracted table row is accounted for. Money fields are cross-checked (crossfooting). Bank statements are balance-checked. Every field links back to its source in the document.

Unsupported methods on registered API paths return an empty 405 Method Not Allowed response with an Allow header listing supported methods. HEAD is supported wherever GET is registered; OPTIONS keeps its existing preflight behavior. Unknown paths remain 404. Maintenance and canonical-host redirects still take precedence.

Server:https://arkrel.com

This site

Client Libraries
Shell Curl

businesses

​
businesses Operations

List your businesses

​

Lists only the businesses the signed-in person belongs to.

Responses

  • application/json
  • 401

    Sign in required. Destructive actions and export creation require fresh step-up authentication.

  • 403

    Membership, role or same-origin check failed.

Request Example for get/app/api/orgs
curl http://localhost:53931/app/api/orgs \
  --cookie 'better-auth.session_token=YOUR_SECRET_TOKEN'
Ask AI Agent
[
  {
    "id": "org_client",
    "name": "Client business",
    "slug": "client-business-abc123",
    "plan": "free",
    "retention_days": 30,
    "role": "owner"
  }
]

Success