Skip to content

Developer platform / source-derived contract

Send business events. Receive controlled financial state.

Integrate through one versioned contract with exact decimals, stable external identities, scoped credentials, atomic idempotency, typed errors, signed delivery, and a sandbox that can be reset without destroying its evidence history.

Integration rule

Send what happened in the business. Invarent applies approved accounting policy and returns accepted, held, rejected, posted, reconciled, and exception state.

Production contract

The runtime is the documentation source.

Runtime operations
253generated from API source
Canonical target
217/217operations represented
Route mismatches
0contract-to-controller drift
Financial browser writes
0all commands cross the API
CONTRACT / 01

Canonical events

Versioned schemas carry source identity, exact money, dates, dimensions, external IDs, and evidence.

ACCESS / 02

Scoped credentials

OAuth client credentials and API keys carry tenant identity, scopes, lifecycle state, and rotation controls.

RETRY / 03

Atomic idempotency

A retry cannot create a second financial effect, and a changed payload cannot reuse an earlier key.

DELIVERY / 04

Signed webhooks

Ed25519 signatures, DNS revalidation, retries, dead letters, replay, and delivery evidence close the loop.

First controlled lifecycle

Provision, create, submit, approve, post, verify.

  1. 01

    Provision a sandbox tenant

    Create a legal entity, books, period, chart template, golden posted entry, and scoped integration credentials.

  2. 02

    Create and submit the journal

    Use an idempotency key and exact decimal lines. Submission freezes the content that will be reviewed.

  3. 03

    Approve through a separate actor

    The approval grant binds actor, scope, expiry, and the journal content hash. Self-approval fails closed.

  4. 04

    Post and read the proof

    Posting, balances, audit event, usage record, idempotent response, and webhook outbox commit in one transaction.

A controlled starting point

Start from the real production contract.

Use the hosted OpenAPI document and generated TypeScript or Python SDK, then prove the complete lifecycle inside an isolated sandbox.