Skip to main content

Update a flow

PATCH 

/v1/flows/:flow_id

Changes the flow's settings: name, description, confirmation message, visibility and notify contacts. Omitted keys keep their value. Ownership, status and versions are never writable here, and the record action has its own endpoint. Making a private flow public claims its keywords across Hop; 409 code_conflict when one is already taken. It also opens the flow to anyone: a public flow accepts a submission from any phone number that texts its keyword and creates the contact on first use, where a private flow accepts only contacts your organisation already has. Requires the flows:write scope.

Request​

Responses​

The flow, as GET /v1/flows/{flow_id} now serves it.