List workflow submission journeys
The per-submission journeys behind the aggregate figures: for each submission that transitioned inside the window, its status, current step, start and finish, elapsed time, step count, whether it was sent back, and every stage it passed through. The operators are side-loaded, so their names are available without a second read.
Takes the same required window and the same optional cohort filters as the aggregate, so a page of journeys always reconciles with the figures above it.
Send Accept: text/csv (or format=csv) for the export instead of a page:
shape=transitions for one row per transition, shape=summary for one row per
submission. The export ignores pagination and covers the whole window.
A window the server had to bound is reported as meta.stats.truncated on the JSON
response, and as an X-Insights-Truncated header on the export, where a
spreadsheet cannot carry the caveat itself.
Served by a hand-written handler rather than a generated one, because the resource is computed rather than stored.
Authorizations
Session token for authentication.
Path Parameters
The unique identifier for the workflow.
Query Parameters
Narrows the transition records the figures are computed from.
The reporting window is required — an unbounded window would mean aggregating the whole collection, so it is rejected rather than served:
ge(created_at,xxx): the start of the window. Required.le(created_at,xxx): the end of the window. Required.
The cohort filters are optional and mutually exclusive. Both resolve to a set of submissions server-side, through the operation a submission captured:
eq(scheme,xxx): only submissions whose payload operation belongs to the scheme.eq(contract,xxx): asscheme, expanded across every scheme in the contract.
A submission that captured no operation cannot join a scheme or a contract, so it is invisible to both cohorts. Unscoped figures include it.
The organisation is not a filter — it is the organisation that owns the workflow definition in the path.
For more information on using named filters, see the docs
1The field to order the journeys by. One field only, and the schema refuses a second: there is no secondary sort behind it, so a second value would have had no effect on the order it came back in.
Defaults to -started_at, the most recently started first. Submissions still in
progress have no elapsed time, so they sort last under both elapsed_minutes and
-elapsed_minutes.
1started_at, -started_at, elapsed_minutes, -elapsed_minutes Limit the number of resources returned by the API
x >= 1Offset the resources returned by the API
x >= 0Asks for the CSV export rather than a page of journeys. format=csv is
equivalent to sending Accept: text/csv, and exists so the export is a plain
URL — the form a browser download or a scheduled delivery can use without
setting a header.
csv The shape of the CSV export. transitions writes one row per transition — the
stage-by-stage trail behind each submission. summary writes one row per
submission. Ignored unless CSV was asked for.
transitions, summary Response
A page of the workflow's submission journeys, or the whole set as CSV when
text/csv was asked for.
Document level meta about the resources on the server in list endpoints.