Search cards across flows

Runs a card search across every flow accessible to the authenticated user, instead of restricting the search to a single flow. Use this endpoint when the search needs to span cards from more than one flow at once; to restrict the search to a specific flow, use the per-flow search endpoint (/v1/filters/flows/{flowId}/search).

The request envelope is exactly the same as the per-flow search endpoint: it requires order, orderBy, fields (the path projection returned per card) and conditions, a non-empty list of condition tree nodes, with the scope field (any, all or sum) required on every node. The request is not paginated — page and pageSize are not accepted and return a 400 error if present.

Since the search spans multiple flows, each returned card includes the identifier of the flow it belongs to, so the origin of the results can be distinguished. As with the per-flow search, using an incompatible path or operator can result in an internal server error instead of a validation message — we recommend checking the available paths beforehand.

Respostas

🟢200Cards found

application/json

List of cards, from any flow accessible to the authenticated user, that match the given conditions, projected by the paths indicated in fields and sorted according to order/orderBy.

Bodyapplication/json

🟠400Invalid search envelope

🔴500Internal error evaluating the condition

curl --location '/v1/filters/search' \ --header 'Content-Type: application/json' \ --data '{ "order": "asc", "orderBy": "card.enteredCurrentPhaseAt", "fields": [ { "path": "card.title" }, { "path": "card.value" } ], "conditions": [ { "scope": "any", "path": "card.value", "operator": "gte", "value": 0 } ] }'

Search cards across flows

Requisição

Respostas