USuseboom
Initiatives

Participant run steps

Changed on

The participant's node-by-node journey run timeline (most recent first): which nodes ran, the routing signal each emitted, and bounded handler output/error. Engine execution history — for what the customer said, use the messages endpoint.

get/api/v1/initiatives/{id}/participants/{participantId}/steps

Request

  • Base URL
    https://www.useboom.ai
  • Auth
    HTTP bearer

Path parameters

idstring required

Initiative id.

participantIdstring required

Participant id, as returned when adding or listing.

Query parameters

limitinteger

Most-recent steps to return (default 50, max 200). Bounded tail — no older-page cursor; compare against totalSteps.

includeBodyboolean

Include HTTP_REQUEST bodies in step output: the response body (verbatim from the third party — may carry PII) and the resolved requestBody (credential secrets, env values, and document URLs are always masked at capture). Also includes the transcriptSummary and extractedData of a PLACE_CALL step and the eligibility reasoning of a SEND_REWARD step (both quote the customer). Defaults to false: bodies are stripped; failure reason is always included.

Response

Success

participantIdstring required
totalStepsnumber required

Full step count, even when more than limit were returned.

next_cursorunknown required

Changes