---
title: "Get Estimates By Group Filter"
method: POST
path: "/estimate/group/filter"
---

# Get Estimates By Group Filter

`POST /estimate/group/filter`

## Request

- Base URL: `https://dc-region.zuperpro.com/api`
- URL: `https://dc-region.zuperpro.com/api/estimate/group/filter`
- Auth: API key in header `x-api-key`

Kanban board lists: per-status paginated estimate lists, grouped by `estimate_status`. Same fixed-status-group model as Get Estimates Summary — no `job_category_uid`-style dynamic grouping field exists for Estimate.

Each estimate in the response uses a fixed projection (not configurable) — note that `fields_to_select` has no effect on this endpoint even though it's accepted on the plain Estimate list endpoint. The response field `sold_by_user` is renamed to `sold_by`; `created_by` keeps its name. `cpq_status` is not included in the projection.

## Request body

- object
  - `sort` 'ASC' | 'DESC'
  - `sort_by` 'created_at' | 'updated_at' | 'estimate_date' | 'total'
  - `count` integer: Max estimates returned per status group.
  - `filter_rules` object[]
  - `filter_rule_operator` 'AND' | 'OR'

## Response `200`

200

- object
  - `data` object[]
    - `status` object
      - `status` string
      - `status_name` string
    - `count` integer
    - `estimates` object[]

## Changes

- **2026-11-03** `3c21bc232e16`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/zuper/apis/zuper-pro-api/changes/estimate/group/filter/post.md)

---

[API](https://skmtc.dev/zuper/apis/zuper-pro-api.md) - [All operations](https://skmtc.dev/zuper/apis/zuper-pro-api/llms.txt) - [OpenAPI document](https://skmtc.dev/zuper/apis/zuper-pro-api/revisions/3c21bc232e16?raw)