Changelog and versioning

The promise for v1

• May change without notice: new endpoints, new optional query parameters, new fields in answers, new values in code lists. Ignore what you don’t know.
• Never changes in v1: a field removed or renamed, a field’s type changed, an endpoint removed, a required field added to a request. A test in our build compares every change to the published description and fails on any of these, so it can’t slip out by accident.
• Every change to the published description gets an entry below — another test fails the build until it has one.
• If v1 ever needs one of those, it comes as v2 beside v1, and v1 keeps working for at least 12 months after v2 is announced here.

Changes

2026-10-07 — examples and wording, no change to the API

• The examples of an order ack now show acked_version equal to the order’s new version: an order ack moves the order, and the ack is kept at the version it made. In the POST /acks example each payment’s acked_version is its own version.
• The token description says what the sandbox issues: ordinary sfi_live_ tokens. The test prefix comes only from a copy of Slflo you run yourself.

2026-10-07 — v1

The first public version: orders, invoices, payments and returns to pull and ack; the seq counter for invoices, receipts and credit notes; customers, branches, units, products, price lists, prices and balances to push by your keys, alone or in batches; lookup and code lists; the public OpenAPI description.