Platform
Developer API
Infrastructure that cannot be driven programmatically is a product, not infrastructure.
What it changes
- Tenant-scoped by constructionEvery credential belongs to a tenant, and the same three isolation layers apply to an API request as to a session.
- Idempotency is required, not optionalEvery state-changing call takes an idempotency key, because a retried request that creates a second payment is the failure mode that matters.
- Events, not pollingDomain events are written in the same transaction as the change that produced them and relayed afterwards, so a consumer learns about a settlement because it happened.
What it includes
REST resourcesAssets, offerings, subscriptions, payments, holdings and transfers.
WebhooksSigned, retried with backoff, and dead-lettered rather than dropped.
SandboxA separate tier where nothing touches real money and mock providers are permitted.
What this deployment does not do
Stated plainly
The public API is schema and design only in this build — the surface described here is not yet exposed. The outbox relay that would feed webhooks is complete; no subscriber is registered and nothing schedules it.
See it against something real.
Bring an instrument you are actually considering. Structuring it is the only way to judge whether the model fits.