Factuarea APIDevelopers

List the steps of an automation run

List the steps of a single run in execution order, with cursor-based pagination.

  • It serves exactly the same step documents that the run detail embeds; what it saves is payload rather than queries — it leaves out the two frozen snapshots, which are what weigh when you poll every few seconds while a step retries.
  • step_index is the identity of a step: it is what you replay, and what the automation_run.step_dead_lettered event points at.
GET
/automations/runs/{run}/steps
AuthorizationBearer <token>

In: header

Path Parameters

run*string

Query Parameters

limit?integer

Number of objects to return. Integer between 1 and 100. Defaults to 25.

Default25
Range1 <= value <= 100
starting_after?string

Cursor for forward pagination. Use the uuid of the last object on the previous page.

Formatuuid
ending_before?string

Cursor for backward pagination. Use the uuid of the first object on the current page.

Formatuuid

Headers

Factuarea-Version?string

Pin the API version (YYYY-MM-DD, Stripe-style date versioning) for this request; omit to use the key's pinned version, or the latest if none. Unsupported version → 400 unsupported_api_version; malformed → 400 parameter_invalid_format. The effective version is echoed in the Factuarea-Version response header. See the Versioning guide.

Formatdate
X-Active-Profile?string

Operate on behalf of a child company (gestoría master key): pass its public id (UUID v7) and the request runs against that child's data without changing the key's scope, tier or environment (omit to use the key's own company). Invalid UUID → 400 parameter_invalid_uuid; unknown or non-owned id → 404 profile_not_found. See the Acting on behalf guide.

Formatuuid

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json