EPepilot

getJourneyContextUsages

Changed on

Which of the given journey's context parameters are preset by tasks in this org's flow templates, matched structurally against each task's typed journey.context_parameters[].key field and gated on journey_id so a same-named parameter in another journey is never reported. journey_submission triggers are deliberately not reported: a trigger binds a journey, not a parameter. Internal, read-only; part of ER-5240.

post/v1/workflows-definition/journey-context:usages

Request

  • Base URL
    https://workflows-definition.sls.epilot.io
  • URL
    https://workflows-definition.sls.epilot.io/v1/workflows-definition/journey-context:usages
  • Auth
    HTTP bearer

Request body

journey_idstring required

Journey whose context parameters are being checked for usage.

param_keysstring[] required

Context parameter keys to look for, as plain strings.

param_idsstring[]

Accepted and ignored. This service stores context references by name only; the field keeps one request shape across every adapter in this feature.

Response

Success

status'ok' | 'partial' required

partial means the usages list hit its cap and the scan stopped there, before every scannable flow template in the org was examined. ok means the scan reached the end of the scannable population and returned every match found there — it does NOT mean every flow template in the org was examined: the underlying query only returns version = v3 records, so legacy v1/v2 templates never enter the scan, and any record that fails to normalize is silently skipped and logged rather than failing the whole lookup.

scannedinteger required

Count of flow templates examined. This is every scannable flow template in the org, not only templates bound to this journey: the underlying query has no server-side journey filter, so it counts the org's whole scannable flow-template population, up to wherever the scan stopped if status is partial. "Scannable" excludes legacy v1/v2 records (the query filters to version = v3) and any record that fails to normalize (skipped and logged rather than failing the lookup), so this can be lower than the org's true total flow-template count.

Changes