---
title: "Search & list executions"
method: GET
path: "/merchant/workflows/{workflowCode}/executions"
tags: ["Executions"]
---

# Search & list executions

`GET /merchant/workflows/{workflowCode}/executions`

Fetch a list of merchant workflows executions for the given query parameters.

## Path parameters

- `workflowCode` string, required — Machine-friendly code of Workflow.

## Query parameters

- `filter[merchantReference]` string
- `filter[holderReference]` string
- `filter[workspaceId]` string
- `filter[workflowCode]` string
- `filter[workflowVersion]` string
- `filter[lastStatus]` string
- `page[after]` string — Cursor for paging results.
- `page[before]` string — Cursor for paging results.
- `page[size]` integer

## Response `200`

Success.

- object
  - `links` object, required
    - `self` string, required
    - `prev` string
    - `next` string
    - `first` string
    - `last` string
  - `results` object[], required
    - `id` string, uuid, required — ID of this execution.
    - `createdAt` string, date-time, required — When this execution was started.
    - `updatedAt` string, date-time, required — When the last event occurred for this execution.
    - `status` object[], required — Business-case dependent set of status tags of this execution. The order of statuses does not matter and should not be used for any logic.
      - `code` string, required — Business-case dependent status code.
      - `time` string, date-time, required — When this execution status was set.
      - `errors` object[] — The reason why the status was set, absent if the status isn't an error status.
        - `id` string, uuid, required — Unique identifier of the error. Please use this value when reporting an issue to our team, so we can help you faster.
        - `code` string, required — Machine-friendly error code assigned to the error. Check the full list of possible values [here](https://docs.payrails.com/docs/error-codes#list-of-error-codes).
        - `detail` string, required — Human-readable description about the error, its cause, and resolution.
        - `docUrl` string — Link to the specific documentation about this particular `code`.
        - `reason` object — Metadata providing more details about the reason of the error. The structure of this object varies according to the `code`.
    - `merchantReference` string, required — Merchant-provided reference for the Execution. Commonly, the identifier of the order on the Merchant's system.
    - `holderReference` string, required — Merchant-provided reference for the transaction counterparty, i.e. the paying consumer.
    - `workflow` object, required — Workflow template from which the Executions are created.
      - `code` string, required — Machine-friendly code of Workflow.
      - `version` integer, required — Version of a Workflow Configuration.

## Other responses

- `400` — Bad Request.
- `401` — Unauthorized.
- `403` — Insufficient Scope.
- `404` — Not Found.
- `429` — Too Many Requests.

---

[API](https://skmtc.net/payrails/apis/payrails-api-reference.md) · [All operations](https://skmtc.net/payrails/apis/payrails-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/payrails/payrails-api-reference/revisions/9dd2f0158582/schema)