Developers
Financial infrastructure, available through APIs.
Ingest transactions, reconcile them and read the results programmatically, with webhooks for every state change.
Conceptual API
One call to reconcile a transaction.
Send a transaction and its reference; get back a match, or an exception with a reason.
API shapes are illustrative until documentation is published. No keys, endpoints or latency figures here are live.
# Conceptual API: shapes are illustrative.
POST /v1/transactions/reconcile
Authorization: Bearer dm_test_••••••••
Idempotency-Key: 9f1c2a7e
{
"transaction_id": "txn_48291",
"reference": "INV-1024",
"amount": 50000,
"currency": "INR"
}Start here
Three places to begin.
Design principles
Conventions that make integration predictable.
- Idempotent writesEvery write accepts an idempotency key, so retries are safe.
- Typed errorsErrors carry a stable type and a machine-readable detail.
- Cursor paginationLists page by cursor, so large reads stay consistent.
- VersionedPaths are versioned, and changes are additive within a version.
- Event-drivenState changes emit signed webhook events.
- Test modeSeparate keys and data for safe experimentation.
Documentation
Documentation outline.
The reference is in preparation. This is the planned structure, so you can see what it will cover.
- 01Getting startedWorkspaces, environments and API keysIn preparation
- 02Transaction modelFields, types and lineageIn preparation
- 03IngestionConnectors, files and the ingest APIIn preparation
- 04Matching and rulesRule syntax, tolerances, scoringIn preparation
- 05ExceptionsTypes, states and the approval workflowIn preparation
- 06WebhooksEvents, signatures and retriesIn preparation
- 07Errors and limitsError types, rate limits, idempotencyIn preparation
- 08SecurityKeys, scopes and workspace isolationIn preparation
Make every financial transaction explainable.
Connect your financial systems, reconcile transactions automatically, and build a reliable source of financial truth.