Roadmap

This page is deliberately honest about what the public API does not offer yet, so you can plan around it. Everything below is planned but not implemented — build against the endpoints documented in this reference, not these.

Self-service API keys

There is no self-service API-key issuance in the public API today. Integrations authenticate with the standard login and refresh token flow — obtain an access token with POST /auth/login and refresh it as needed (see API keys). Long-lived, self-managed API keys with scoped permissions are planned.

Official SDKs

The API is plain JSON over HTTPS and works with any HTTP client today — copy-paste code samples cover the common languages, and you can generate a client from the OpenAPI document. Official, hand-maintained client libraries (for example JavaScript/TypeScript and Python) are still on the roadmap.

Outbound event webhooks

The only webhook today is the inbound, signature-verified payment-gateway callback. Outbound event webhooks — letting your systems subscribe to changes such as a new invoice or a recorded payment — are planned. Until then, poll the relevant list endpoints.

A complete, authoritative spec

A representative OpenAPI 3 skeleton and Postman collection are available now for the auth flow and the most-used endpoints. A complete, auto-generated OpenAPI description covering every endpoint — kept in lock-step with the API — is planned; until then the exhaustive surface lives in the API catalog.