Developers

Versioning and changes

How the SKUFlow API changes over time and how to write clients that keep working.

The SKUFlow API has one live version, served at https://app.skuflow.ai/api. There is no version number in the path.

What changes

SKUFlow adds to the API often: new endpoints, new optional inputs, new fields in answers and new webhook events. The app, SKUFlow AI and the MCP server use the same API, so a new feature in the app arrives in the API the same day.

Write your client so these additions never break it:

  • Ignore fields you don't know. Answers gain fields over time.
  • Don't fail on new enum values. A status list such as an order's can gain a value; treat an unknown one as "other".
  • Subscribe to the webhook events you need by name, or ignore event types you don't know.
  • Send only the inputs you mean to set. New inputs are optional and leave things as they were when you leave them out.

Event payload versions

Each event type has a version, shown with every event in the event log (Settings → Developers → Event log). If an event's data ever has to change in a way that isn't an addition, its version goes up.

Stay up to date

  • The OpenAPI document at https://app.skuflow.ai/api/openapi.json always describes the live API. Generate a client from it, or diff it to see what changed.
  • This reference is generated from the same definitions. See API reference.
  • The changelog at skuflow.ai/changelog announces new features.

On this page