API reference

API reference

The Arcanum API serves the data the hosted app shows: wallets, payments, approvals and events indexed from Arc. It never signs or sends transactions. When the app helps you change something, the API prepares an unsigned transaction and you sign it in your wallet.

Agents do not need the API to pay; the SDKs talk to Arc directly.

Access

Every protected request uses a Sign-In with Ethereum (SIWE) session. Your organisation is taken from the session, never from the request, so a request cannot read another organisation’s data.

Areas

AreaWhat it covers
authSign-in sessions.
orgYour organisation and its members.
walletsWallets, their policies and agents.
agentsAgent details, payments and risk events.
transfersPayment history with filters.
escalationsHeld payments, and unsigned approve or reject transactions.
vendorsVendor lists, and unsigned vendor changes.
policiesUnsigned policy changes and their transaction records.
anomaliesRisk events and their review state.
eventsThe raw event stream.
analyticsTotals: value governed, active agents, payments blocked, pending approvals.
receiptsPayment decision receipts.

Receipt endpoints

Agent runtimes can use these REST endpoints directly:

MethodPathPurpose
POST/api/receiptsRequest a receipt for a payment intent.
POST/api/receipts/{id}/evidenceLink a transaction to a receipt.
POST/api/receipts/verifyVerify a receipt.
GET/api/receipts/issuersList the receipt issuer keys.

See Receipts for what a receipt contains.