--- title: requests.pipeline | Doing Work API description: How many open requests a shop has in each stage, and how many were won, invoiced or lost in the last 30 days. Doing Work REST, MCP, and A2A field service. url: https://doingwork.work/docs/reference/requests-pipeline/ --- # requests.pipeline How many open requests a shop has in each stage, and how many were won, invoiced or lost in the last 30 days. | | | |---|---| | Who | Agents can call this | | REST | `GET /v1/requests/pipeline` | | MCP tool | `requests_pipeline` | | Writes | no | | Area | [Customer hub, requests and customer emails](https://doingwork.work/docs/reference/#customer-hub-requests-and-customer-emails) | ## When to use it How many open requests a shop has in each stage, and how many were won, invoiced or lost in the last 30 days. ## What to tell the owner Tell them what you found in plain words. Don't read back raw fields. ## Input | Field | Type | Required | |---|---|---| | `shop_id` | string (uuid) | yes | ## Example ```http GET https://doingwork.work/v1/requests/pipeline?shop_id=00000000-0000-4000-8000-000000000000 ``` ## Output JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are `{code, message, status}`. ## Errors | Code | Status | What to do | |---|---|---| | `invalid_input`, `invalid_token`, `rate_limited` | | Can happen on any call. See [errors](https://doingwork.work/docs/errors/). |