Changelog
What changed, and what counts as a breaking change.
API stability
We version the API in the path (/v1). Within a version:
Breaking changes — we will not make these without notice and a migration path:
- removing or renaming a field, an endpoint or an error code;
- changing the meaning or type of an existing field;
- adding a required request field;
- changing the signing algorithm or the string to sign;
- removing an order status or a webhook event type.
Additive changes — we make these without notice, and your integration must tolerate them:
- new optional request fields;
- new response fields;
- new webhook event types;
- new endpoints;
- new error codes.
Two obligations this puts on you
Ignore fields you do not recognise, and ignore webhook type values you do
not recognise. A client that rejects an unknown field or event breaks on a
change that is not supposed to break anything.
Changes are announced here and by email to your registered contact.
Changes
2026-09-04
- Documentation: a plain-language Overview section — what the API is, how an order works, use cases, a glossary and an FAQ — for product, finance and compliance readers, and a rewritten welcome page.
- Documentation: webhooks, signature verification, authentication and the error catalogue are documented. The reference is ordered by integration workflow and the OpenAPI spec is downloadable.
2026-09-02
POST /v1/orders/buy— create a buy order against a quote. Both legs now have a create route.
2026-09-01
- Outbound webhooks:
order.funds_confirmed,order.settled,order.rejectedandorder.expired, signed with HMAC-SHA256 and retried. - Partner API documentation published.