Historial de cambios

Historial en inglés. Se conserva el texto publicado y su contexto temporal; para implementar una integración, consulta la referencia actual.

This is the public changelog for the Fluyio API. Every meaningful change — new endpoints, new fields, behaviour changes, fixes — is recorded here with the date it reached production.

How versioning works

The API uses date-based versions set through the Fluyio-Version header. There is one published version, 2026-05-15, and it is also the default when the header is omitted.

curl https://fluyio.com/api/v1/subscribers \
  -H "Authorization: Bearer fly_live_xxx" \
  -H "Fluyio-Version: 2026-05-15"

• Non-breaking changes (new fields, new endpoints, new resources) ship to the current version and are listed here.
• Breaking changes will ship as a new dated version. The previous version will stay available for at least 12 months after the new one is published, and the sunset will be announced here and by email to accounts still using it.

Read more in API versioning.

Releases

What counts as breaking?

We treat all of the following as breaking and will bump the API version for them:

• Removing or renaming a field, endpoint, parameter or enum value.
• Changing the type or shape of a response field.
• Adding a new required parameter.
• Tightening validation so that previously valid requests fail.
• Changing the meaning of a field or status code.

These are not breaking and ship into the current version:

• Adding new fields, endpoints or resources.
• Adding new optional parameters.
• Adding new error codes within an existing error type.
• Performance improvements, bug fixes and infrastructure changes.

Reporting a regression

If something that worked yesterday does not work today, write to [email protected] with:

• The request_id from the failing response (also in the Fluyio-Request-Id header).
• The Fluyio-Version header you sent.
• A minimal reproduction (cURL is ideal).