Changelog
The public API changelog starts here. There will be no entries for earlier versions: there is nothing to reconstruct them from, and inventing them after the fact is worse than having no changelog at all.
Empty for now — and that is not a placeholder
What will land here
Only what is visible from the outside and can break a working integration.
- Operations added, renamed or removed from the reference.
- New required request fields and response fields that disappeared.
- Enum changes: new order statuses, task types, asset kinds.
- New response codes and new machine-readable reason values in error bodies.
- New realtime channels and events, and changes to payload shapes.
How to track changes right now
Until the changelog exists, the specification itself is the only reliable signal.
The caveat without which this advice would be harmful: this is the info.version field, and it comes from the backend generator’s default — it has never changed. You cannot treat it as an API version number. What does work: save the specification file and diff it against a fresh copy — changes to operations and fields show up immediately.
Spotted a change that is not in the documentation? Tell us: Support
Feed this page to an AI
spec 0.0.1