Skip to main content
May 11, 2026 Documentation update No migration required

​
Affects

Teams reading the public Flowker API reference. This update applies to the public documentation portal. It does not change the runtime API behavior.
The public documentation portal is the customer-facing reference. Repository source files should not be treated as integration artifacts or downloaded API specifications for client use.

​
What changed

​
Operational endpoints removed from public API reference

The following Flowker endpoints no longer appear in the public API reference:
  • /health
  • /version
Flowker still serves both. They are simply no longer presented as customer-facing integration endpoints.

​
Impact

This is a documentation update. It narrows the public Flowker API reference to the integrator-facing surface. No product behavior changed.

​
What you need to do

1
Do not use the public Flowker API reference as the source for operational health or version checks.
2
Keep operational monitoring tied to internal documentation and deployment-specific configuration.
3
Do not treat repository source files as client integration artifacts. Use the documentation portal as the customer-facing reference.

​
Deadline

None.

​
Why

Operational endpoints are useful, but they are not the same thing as customer-facing integration endpoints. Removing them from the public reference keeps the documentation clearer.

​
Resources