Post Your First Journal in 5 Minutes
The fastest path to value in Paprel — get sandbox keys, authenticate, post a balanced double-entry journal over REST, and read it back from the ledger.
Documentation
Reference docs, integration walkthroughs, OAuth setup, MCP scopes, and architecture notes for platform teams.

OpenAPI explorer, journal primitives, webhooks, authentication, and MCP tools.
Open UnderstandThe write path, tenant isolation, reliability model, and deployment options — the map your reviewers will ask for.
Open AgentsGoverned tool access for AI agents — OAuth scopes, company-bound endpoints, and audit.
OpenThe fastest path to value in Paprel — get sandbox keys, authenticate, post a balanced double-entry journal over REST, and read it back from the ledger.
A guided walkthrough from sandbox keys to a live P&L — extend the chart of accounts, invoice a customer, record a payment, and read the ledger entries back over the API.
How Paprel ships — managed multi-tenant with tenant-pinned regions, white-label under your brand with partner attribution, or private deployment in your cloud — and how to choose, with what stays identical across all three.
How Paprel is layered — company-per-tenant isolation enforced at the data layer, an append-only double-entry ledger that rejects unbalanced postings, a workflow layer that compiles documents into journals, and reports derived live from the same rows.
How Paprel's write path stays safe under retries — idempotent writes, balanced-or-rejected validation before the ledger, signed webhooks with content hashes, and recovery from the GL export instead of fragile redelivery machinery.
How Paprel API authentication works — create client credentials, exchange them for a short-lived OAuth 2.0 access token, sign write requests with x-data-signature, and keep every secret off the frontend.
Build the full expense lifecycle over the API — capture a direct expense, raise a vendor bill behind an approval gate, pay it, and read the resulting double-entry journals back from the ledger.
How to keep a marketplace's books straight over the API — record each order as one balanced journal that splits gross into seller payable and commission revenue, pay sellers out, and read per-seller balances back from the ledger.
Wire a recurring subscription into real books — a recurring invoice that posts revenue, payment recording, a manual deferred-revenue schedule for annual prepay, and journals you can read back.
How to run accounting under your own brand — provision a company per customer, define roles against module permissions, issue tenant-scoped OAuth tokens, and hand every tenant a working set of books.
Use sandbox for developer testing with no billing. When you are ready for real workflows, start production on a monthly plan with a 14-day free trial.