Skip to main content
KarFlows should keep public API behavior stable.

​
Current version

Some legacy endpoints are not versioned yet, such as:
They are still treated as stable customer APIs.

​
Compatibility rules

KarFlows can safely add:
  • New optional request fields.
  • New response fields.
  • New log fields.
  • New enum values when documented.
KarFlows should avoid changing:
  • Required fields.
  • Token behavior.
  • Existing status names.
  • Existing endpoint paths.
For major changes, add a versioned endpoint:
Keep older endpoints running until customers migrate.