Create Nurture
POST /nurtures
Create a nurture.
sequence_kind is pinned to nurture by the app and re-validated there,
so the nurture-specific channel rules fire even though this endpoint never
accepts the field. user_email defaults to the identity the key was
minted under; a personal nurture owned by anyone else is a 403.
Authorizations
Parameters
Header Parameters
Request Body required
Create a nurture.
sequence_kind is NOT accepted: the app pins it to nurture server-side
and re-validates, which is what makes the nurture-specific channel rules
fire. A client-supplied kind would either be ignored or, worse, look
honoured.
object
Sending channels to attach.
object
Stop nurturing a contact once they reply.
Append the visible reply-opt-out CTA to email bodies.
True makes the nurture visible org-wide. Requires an Admin or Owner role; see this router’s note on org-scope promotion.
Nurture name.
The ONE mailbox this nurture sends from. Required: a nurture is pinned to a single sender so its consented audience always hears from the same address, and every email channel attached must use it. validate_nurture_rules rejects a nurture without one, so this is required here rather than left to fail deeper in.
Keep follow-ups in the original email thread.
Initial status. Nurtures start drafted.
Sequence steps, in order.
object
Responses
201
Successful Response
object
One nurture sequence.
object
422
Validation Error