X1 and C4

Surfaces and the API

114 endpoints, and a retry that cannot post twice. Both portals are built on this API. There is no privileged internal route, no second data path, and nothing an integrator is locked out of that our own screens use.

114 endpointsTwo surfacesIdempotent by key

Send it twice. Nothing happens twice.

The second call does not re-execute. It returns the stored response from the first, which is why the body is identical rather than merely equivalent. A client that times out mid-transfer can simply try again instead of reconciling by hand to find out whether the first attempt landed.

POST/v1/transfersFirst callSent again
{
idempotency_key: “9f2b41c6-7a30-4e51-9b8e-2c4d6f1a8e55”
debit_account: “acct_01HQZ4N8K2”
credit_account: “acct_01HQZ4N8M7”
amount: {
value: “24500.00”
currency: “EUR”
}
reference: “TRF-7741-0092”
}
201200CreatedOKResponseReplayed
{
id: “txn_01HQZ55PD3”
status: “SETTLED”
posted_at: “2026-10-28T14:20:11Z”
entries: [
0: {
account: “acct_01HQZ4N8K2”
side: “DEBIT”
amount: “-24500.00”
currency: “EUR”
}
1: {
account: “acct_01HQZ4N8M7”
side: “CREDIT”
amount: “24500.00”
currency: “EUR”
}
]
}
IdempotentThe body is identical because it is the stored response, not a second execution. One transaction in the ledger, two calls in the log, and a client that may retry a timeout without knowing whether the first attempt landed.

Two surfaces.

/v1

Administration

Everything an operator does: parties, applications, decisions, accounts, transactions, cases, limits, reporting.

/client/v1

Client

Everything a customer does: registration, second factor, onboarding, accounts, statements, transfers, payees.

Four rules the whole API keeps.

House standards, applied across all 114 endpoints rather than to whichever ones were written most recently.

Every mutation takes a key

No idempotency key, no write. It is a required header rather than an optional nicety, because the retry you did not plan for is the one that posts twice.

Money is a string

Amounts cross the wire as decimal strings with an explicit currency. Nothing in this API will hand you a float and hope.

Identifiers are opaque

Prefixed, sortable, and not a sequence. You cannot infer our volumes from an id, and neither can anybody else.

Errors name the rule

A rejection says which constraint refused and what it was evaluating, because an integrator debugging a 422 at four in the afternoon should not have to guess.

What it holds to.

The things that matter to whoever maintains an integration two years after it was written, rather than to whoever writes it this week.

  • A published versioning policy. A breaking change gets a new version and the old one keeps answering, with the sunset date given in writing rather than in a changelog nobody is subscribed to.
  • Scoped credentials per partner, so revoking one integration does not revoke the others.
  • A generated reference that cannot describe an endpoint the code does not serve, because it is produced from the same definitions the server routes on.
  • Outbound webhooks with signed payloads and replay, so an integration does not have to poll to find out what happened.

Talk to whoever wrote it.

There is no sales engineer layer. A demo is with the people who would be answering your integration questions anyway.