API/Roadmap
v1.0.0-beta.mdGet API keys
Reference

Roadmap

Intentions, not contracts. Nothing on this page answers yet, and nothing anywhere else in these docs is described in the future tense.

ItemWhat it will be, and why it is not here yet
The /v1 REST façadeResource paths and bearer keys over the same engine. Deferred to before the first external client: with zero integrations today, changing later breaks nobody, while documenting a façade that does not answer breaks everybody.
Dated versioning (Sidaxis-Version)A change policy worth publishing once there is a client to protect.
Published rate limits and rate-limit headersReal ceilings, measured, with headers on every response. Today only the alias endpoint's limits are published, because those are the only ones we are prepared to promise.
Cursor pagination on mandate readsmandate-get currently returns a list by effective status, and a single-mandate read includes the last 100 consumptions.
A public status page with measured availability and targetsNo SLA is published until it is measured.

Not on this page

The MCP server. It is in production at https://api.sidaxis.com/functions/v1/mcp with nine tools — see MCP.

Sidaxis is the human authorisation layer. It never moves money, holds funds or settles. The machine-readable contract is openapi.yaml.
Sidaxis API documentationQuickstartAuthenticationHosted or headlessSandbox and productionIdempotencyRate limitsErrors and refusalsField namesWebhooksAssuranceThe document ruleAlias availabilityMerchant themeMCP serverCompatibilityStatusRoadmapChangelogIdentityEnroll an identityRecognise a personDisclose an attributeMandatesThe eight scopesIssue a mandateCheck an actionConsume a mandateRead a mandateRevoke a mandateReceiptsRead a merchant's receiptsVerify a receiptHosted sessionsCreate a hosted sessionConsume a hosted sessionOne Face for agents