Versioning and stability

Each API carries its major version in the path — /collect/v1, /oms/v1, /delivery/v1, /v1/ai-tools. The warehouse interfaces keep the paths of the protocol they reproduce (/V1 for T-Data), so existing warehouse software works unchanged.

Within a version we only make additive changes:

• new endpoints, new optional parameters, new fields in responses;
• new values in fields documented as open lists (for example event kinds or tracking statuses);
• new error codes for new situations.

Build your client to ignore fields it does not know. Removing or renaming a field, changing its type or making an optional parameter required would be a breaking change, and goes into a new version.

Every API reference shows a stability label:

• Stable — in production and in use; changes follow the rules above.
• Beta — in production and supported, but recent: details may still change after feedback from the first integrations. Breaking changes on a Beta API are announced in the changelog before they ship, and we contact the integrations we know of.

Every change that affects an integration is published in the Nucleo changelog, which also has an RSS feed. The OpenAPI files on this site always describe what is in production today.