Flows
Replace a flow
Beta. The request and response shapes may still change.
Overwrite a flow in place. The body is the whole flow, not a patch: the recipes you send replace the existing references entirely.
The flow identifier does not change, so a flow already wired into your product can have its recipes swapped without touching the calling code.
PUT
Replace a flow
The body is the whole flow: the
recipes you send replace the existing references entirely, so send the full list even when adding one.
The identifier doesn’t change. This is what makes a flow the right thing to hard-code in your product - you can retire a recipe, add a shadow one beside it, or reorder the references without a deploy on your side.
Replacing a flow that does not exist answers 404 rather than creating it.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The flow identifier.
Example:
"flo_01jc0t6fwwfgfsq1md24mhyztj"
Body
application/json