---
title: "Get Purchase Order Summary"
method: POST
path: "/purchase_orders/summary"
---

# Get Purchase Order Summary

`POST /purchase_orders/summary`

## Request

- Base URL: `https://dc-region.zuperpro.com/api`
- URL: `https://dc-region.zuperpro.com/api/purchase_orders/summary`
- Auth: API key in header `x-api-key`

Operates on Purchase Orders. In the Zuper client app this module is labeled "Purchase Order" for most companies, and "Material Order" for companies in the roofing industry — the API and data shape are identical either way. Purchase Orders and Work Orders (Service Orders) share the exact same underlying schema and endpoints; they're distinguished only by the `purchase_order_type` field (`PURCHASE_ORDER` here) and the `/purchase_orders` vs `/service_orders` route prefix. Returns order counts/totals overall and broken down by status, plus an `OVERDUE` bucket (orders past their due_date in an active pre-fulfillment status).

## Request body

- object
  - `filter_rules` object[]
  - `filter_rule_operator` 'AND' | 'OR'

## Response `200`

200

- object
  - `type` 'success'
  - `message` string
  - `data` object
    - `total_purchase_orders` object
      - `count` integer
      - `total` number
    - `count_by_status` object[]
      - `status_name` string: One entry per status value, plus a synthetic "OVERDUE" bucket.
      - `count` integer
      - `total` number

## Changes

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

[Operation history](https://skmtc.dev/zuper/apis/zuper-pro-api/changes/purchase_orders/summary/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)