Warning: a direct call to this simple listing is not available — the server returns a 404 error (route does not exist), rather than a resource-not-found 404.To retrieve every card of a flow, results must be aggregated by iterating over phases: first obtain the flow's list of phases, then call the phase-scoped listing endpoint (GET /v1/flows/{id}/phases/{phaseId}/cards) once per phase, summing the results. When the goal is to find cards matching a specific term, prefer the search endpoint (GET /v1/flows/{id}/cards/search), which operates over the whole flow in a single call.
Requisição
Parâmetros de Caminho
Respostas
🟠404Route unavailable
application/json
Always returned when this route is called directly — a simple listing of every card in a flow is not implemented in this API.
Bodyapplication/json
Request Request Example
Shell
JavaScript
Java
Swift
curl--location'/v1/flows//cards'
Response Response Example
{"message":"Cannot GET /v1/flows/{id}/cards","error":"Not Found","statusCode":404}