Developers
API
This page describes a design, not a live endpoint. Saying so is the point — an API reference for something you cannot call is worse than no page at all.
What it changes
- Tenant-scoped credentialsEvery key belongs to a tenant, and the same isolation layers apply to an API request as to a session.
- Idempotency on every writeA retried request that creates a second payment is the failure that matters, so the key is required rather than optional.
- Errors that say what to doRefusals name what is missing and what can be done instead, in the same vocabulary the interface uses.
What it includes
ResourcesAssets, offerings, subscriptions, allocations, payments, holdings, transfers, distributions and redemptions.
Pagination and filteringStable cursors, because offset pagination over a moving register skips and repeats rows.
VersioningExplicit, with a deprecation policy rather than silent change.
What this deployment does not do
Stated plainly
Not exposed in this build. The schema and the authorization model exist; the HTTP surface does not.
See it against something real.
Bring an instrument you are actually considering. Structuring it is the only way to judge whether the model fits.