Skip to content

Launch Nurture

POST
/nurtures/{nurture_id}/launch

Launch a nurture. THIS SENDS REAL MESSAGES TO REAL PEOPLE.

Proxies the same v2 run flow the app’s Go-Live button uses, so enrollment, schedule and consent checks are identical.

WHY THE PATH IS /launch AND NOT THE APP’S /run/v2

Two reasons, and the second is the load-bearing one.

The v2 suffix is noise: v1 was removed on 2026-04-21, so there is nothing left to disambiguate from on a public surface.

launch rather than run is what gets this operation the right SCOPE. build_scope_policy.EXTERNAL_PATH_MARKERS contains /launch, /send and /publish - the fragments that mean “this reaches the outside world” - and an external-tier operation resolves to the run ACTION, so the key needs an explicit sequences:run grant rather than plain sequences:write. As /run this endpoint classified as an ordinary write, one tier below the identical POST /sequences/{id}/run, which is external. Sending real email to real people is the definition of external, and the customer issuing a key should be able to grant “edit my nurtures” without granting “start sending”.

Authorizations

Parameters

Path Parameters

nurture_id
required

Nurture id.

string

Nurture id.

Header Parameters

X-Target-Org-Id
Any of:
string

Responses

200

Successful Response

object
data
required
object
key
additional properties
any
pagination
Any of:
object
has_next
required

Whether there are more pages

boolean
limit
required

Items per page

integer
next_cursor
Any of:
string
page
required

Current page number (1-indexed)

integer
total
required

Total number of items

integer

422

Validation Error

object
detail
Array<object>
object
loc
required
Array
msg
required
string
type
required
string