Sequences
Preview Step
The step's subject/body rendered for a lead, with the current user as the sender.
API key access
Needs the
sequences:read scope with an API key (ro_pat_...). A signed-in session uses the caller's role.GET
/api/v1/sequences/{sequence_id}/steps/{step_id}/previewAuthorizationBearer <token>
Access token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).
In: header
Path Parameters
sequence_idstring
Format
uuidstep_idstring
Format
uuidQuery Parameters
lead_idstring
Format
uuidHeader Parameters
X-Workspace-Id?string | null
Id of the workspace to act on (must be a member).
Response Body
curl -X GET "http://localhost:8000/api/v1/sequences/497f6eca-6276-4993-bfeb-53cbbbba6f08/steps/497f6eca-6276-4993-bfeb-53cbbbba6f08/preview?lead_id=497f6eca-6276-4993-bfeb-53cbbbba6f08" \ -H "X-Workspace-Id: string"{
"subject": {},
"body": {}
}{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string",
"input": null,
"ctx": {}
}
]
}