> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Flowker: API reference cleanup and v1 endpoints registered

> The public Flowker API reference now removes phantom health endpoints and includes seven v1 endpoints that already exist in the service.

<Badge stroke icon="calendar-days" iconType="regular">May 5, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation update</Badge> <Badge color="purple" size="lg" stroke icon="eye" iconType="regular">Review recommended</Badge>

## Affects

***

Teams using the public Flowker documentation for API discovery, implementation review, or AI-assisted documentation search.

This update applies to the public documentation portal. It does not change the runtime API behavior.

<Note>
  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.
</Note>

## What changed

***

### Phantom endpoints removed

The public API reference no longer shows two endpoints that do not exist in the Flowker service:

* `GET /health/live`
* `GET /health/ready`

Their reference pages were removed so readers do not try to call broken public routes.

### Existing v1 endpoints added to the portal

Seven v1 endpoints that already exist in the Flowker service are now visible in the public documentation portal.

This improves API discovery in the documentation portal and gives documentation search tools a cleaner source.

## Impact

***

This is a documentation update. It removes misleading public reference pages and makes existing Flowker endpoints easier to find.

No product behavior changed.

## What you need to do

***

<Steps>
  <Step>
    Review the newly visible v1 endpoints if you use Flowker.
  </Step>

  <Step>
    Keep health and readiness monitoring tied to internal operational documentation, not the public API reference.
  </Step>

  <Step>
    Do not treat repository source files as client integration artifacts. Use the documentation portal as the customer-facing reference.
  </Step>
</Steps>

### Deadline

None.

### Why

The public documentation should describe the customer-facing API surface clearly. Internal operational endpoints create noise and broken expectations when they appear in the integrator-facing reference.

## Resources

***

* [Create workflow](/en/reference/flowker/create-workflow)