General ledger API

General Ledger API For Platforms

Balanced double-entry journals over REST, an append-only ledger underneath, and a programmable chart of accounts — the same ledger core proven in production today.

Get sandbox keys Read the API reference

Ledger surfaceLive

POST

/v1/accounting/journals

Post a balanced journal — the write primitive everything else compiles down to.

GET

/v1/accounting/journals

Read entries back, filtered by account, reference, or date range.

POST

/v1/accounting/accounts

Provision and extend the chart of accounts — hierarchies, subtypes, currencies.

GET

/v1/accounting/journals/for-entity

Every journal tied to one of your product's entities, by your own ids.

What the ledger guarantees

Balanced or rejected

Debits must equal credits at the API boundary. There is no code path that lets an unbalanced journal through.

Append-only

Posted entries are never mutated. Corrections are new entries that reference what they correct; reversals preserve the original.

Idempotent writes

Retries are deduplicated — resubmitting the same request returns the original result instead of a duplicate entry.

Attributable

Review recorded actor and action information, evidence format and retention for your deployment.

The surface

Four primitives cover most ledger work

POST/v1/accounting/journalsPost a balanced journal — the write primitive everything else compiles down to.

GET/v1/accounting/journalsRead entries back, filtered by account, reference, or date range.

POST/v1/accounting/accountsProvision and extend the chart of accounts — hierarchies, subtypes, currencies.

GET/v1/accounting/journals/for-entityEvery journal tied to one of your product's entities, by your own ids.

See it in the books

From document to ledger, rendered

Journal entries generated behind an invoice in the Paprel workspace — The journal behind an invoice — generated by the document, balanced by the ledger.

General ledger detail report grouped by account with journal identifiers and entity links — The general ledger by account: every entry carries an identifier and links back to its source document.

Built on the ledger

Higher-level workflows compile down to journals

Invoices, payments, expenses, and reconciliation all generate balanced journals against the same chart of accounts — which is why reports always tie out. Use the workflow APIs where they fit and drop to raw journals where your domain is unusual.

Walk the full loop in 20 minutes See raw journals in action: marketplace splits

Then connect the ledger to payments, banks, and your product on the integrations page, or see how it compares to QuickBooks, Xero, and Modern Treasury. For the design decisions behind the API, read the double-entry ledger architecture guide.

Related paths

Place the ledger inside the wider product decision

Journal API

Work directly with journal entries

Create, query, connect, and safely correct the debit and credit entries behind product events.

Explore the Journal API

Accounting engine

See the complete backend

Place the ledger inside a wider system of workflows, reports, controls, events, and tenant isolation.

Explore the accounting engine

Embedded accounting API

See the complete accounting layer

Connect the ledger to workflows, reporting, permissions, webhooks, and MCP-native agent tools.

Explore embedded accounting

API alternatives

Compare systems of record

See how Paprel differs from QuickBooks, Xero, accounting aggregators, and money-movement ledgers.

Compare API alternatives

Evaluate Paprel

Build in sandbox, launch with a production trial

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.

Start 14-day trial Get sandbox keys Talk With Us Explore API Specs

API-First Delivery

Audit-Ready Controls

Sandbox And Guided Rollout