Docs

Record offchain obligations for your customers, find netting loops, collect each party's certificate signature and apply certificates on Arc. Contraflow never signs for anyone: every obligation and certificate carries the party's own signature, and you act for a party only under a permission it signed. Test keys (`cfk_test_`) use Arc testnet. Amounts are integer strings in the currency's minor units. In EIP-712 typed-data responses, `domain.chainId` is a JSON number and `digest` is the payload's hash; other integers stay decimal strings.

Machine-readable spec: /api/v1/openapi.json. Keys are operator-issued. Request one through Contact.

Quick start

1. Ask for a test key (`cfk_test_…`).
2. Have the party sign the permission typed data, then `POST /api/v1/permissions`.
3. Call party-scoped endpoints with `Authorization: Bearer` and `Idempotency-Key` on writes.

Contraflow API · v1.0.0

• /permissions/typed-data
• /permissions
• /permissions/{permissionId}
• /obligations/proposals
• /obligations/proposals/{token}
• /obligations/proposals/{token}/accept
• /parties/{address}/obligations
• /parties/{address}/loops
• /certificates/{token}
• /certificates/{token}/signatures
• /certificates/{token}/apply-transaction
• /certificates/{token}/transactions
• /certificates/{token}/export