---
title: "Search for workflow executions based on payload and other parameters"
method: GET
path: "/api/workflow/search"
tags: ["workflow-resource"]
---

# Search for workflow executions based on payload and other parameters

`GET /api/workflow/search`

Search for workflow executions based on payload and other parameters.
The query parameter accepts exact matches using `=` and `IN` on the following fields: `workflowId`, `correlationId`, `taskId`, `workflowType`, `taskType`, and `status`.
	Matches using `=` can be written as `taskType = HTTP`.
	Matches using `IN` are written as `status IN (SCHEDULED, IN_PROGRESS)`.
The 'startTime' and 'modifiedTime' field uses unix timestamps and accepts queries using `<` and `>`, for example `startTime < 1696143600000`.
Queries can be combined using `AND`, for example `taskType = HTTP AND status = SCHEDULED`.

## Query parameters

- `start` integer
- `size` integer
- `sort` string
- `freeText` string
- `query` string
- `classifier` string
- `topLevelOnly` boolean
- `skipCache` boolean

## Response `200`

OK

---

[API](https://skmtc.dev/orkescloud/apis/orkes-conductor-api-server.md) · [All operations](https://skmtc.dev/orkescloud/apis/orkes-conductor-api-server/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/orkescloud/orkes-conductor-api-server/revisions/6ebf0c14ac41/schema)