POST /api/flows
Create a new flow using an encoded flow definition.
New objects within the flow definition, such as actions, will need to use a
temporary_id field for identification. These will be replaced with traditional id fields
after successful creation.
A successful request will return the new definition to you.
Rate limits:
Burst: 1/s
Steady: 15/m
Daily: 100/d
Scopes:
flows:write
OpenAPI Spec
Servers
- https://a.klaviyo.com
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
revision |
String | Yes |
API endpoint revision (format: YYYY-MM-DD[.suffix]) Default value: "2026-04-15" |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
additional-fields[flow][] |
Array | No |
Request additional fields not included by default in the response. Supported values: 'definition' |
fields[flow][] |
Array | No |
For more information please visit https://developers.klaviyo.com/en/v2026-04-15/reference/api-overview#sparse-fieldsets |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.