Sequences

Launch Nurture

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".

post/nurtures/{nurture_id}/launch

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/nurtures/{nurture_id}/launch
  • Auth: HTTP bearer

Path parameters

nurture_idstring required

Nurture id.

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Response

Successful Response

dataobject required

Changes

No recorded changes to this operation across all 2 revisions of this API.