The API is v1. That path segment is a compatibility promise, and this page is what it means.What will not change inside v1#
Endpoints keep working. A path that exists today will not be removed or repurposed without a deprecation (below).
Response fields are not removed or retyped. A field you read today keeps its name and its type.
Optional request fields stay optional. A field that is not required today will not become required.
Enum values you receive may grow. Handle an unknown value by ignoring it rather than crashing — a new order status is an additive change, not a breaking one.
Error shapes stay put: the error object (code, message) for failures, and the HTTP status codes documented here. What counts as additive, and can ship any day#
New optional request fields.
New fields in a response.
Write clients that tolerate additions: read the fields you need, ignore the rest, and never assert on an exact object shape.Deprecation#
When something must change, in order:1.
Announced in the changelog, with the replacement and a date. 2.
A Deprecation header on responses from the affected endpoint, carrying the sunset date.
3.
At least 90 days before withdrawal. For anything touching orders or payments, 180.
4.
Withdrawn only after that window. A breaking change that cannot be made this way becomes v2, and v1 keeps running while both exist.
Security fixes are the exception: a change that closes a vulnerability may ship immediately, and the changelog will say so.Keeping up#
Regenerate your client from the OpenAPI document. It is generated from the running API, so it is always current. Leave us an address at engineering@numueg.app if you run an integration your business depends on. We tell affected integrators directly before a deprecation, not only through a page. Modified at 2026-09-24 13:03:12