Flows
OpenAPI operations for browser-facing flow orchestration.
Flows resolve a definition for a browser journey, return the current capability step, accept step submissions, and collect client-side events for risk and orchestration.
End a session GET
Previous Page
Start a new flow POST
Resolves a flow definition based on purpose + audience context and returns the first capability step. Creates a new session implicitly unless `session_id` is provided (for step-up / reauth on an existing session). The response contains an `id` field — the flow handle. Use it as the path parameter for all subsequent `/flow/{id}/submit` and `/flow/{id}/event` calls. The response also sets an encrypted `HttpOnly` cookie (`_zflow`) containing the flow's orchestration state (current step, collected data, history). The server is stateless between requests — all flow state lives in this cookie. The browser sends it automatically on subsequent requests.