---
title: "Get Purchase Orders Meta"
method: GET
path: "/purchase_orders/meta"
---

# Get Purchase Orders Meta

`GET /purchase_orders/meta`

## Request

- Base URL: `https://dc-region.zuperpro.com/api`
- URL: `https://dc-region.zuperpro.com/api/purchase_orders/meta`
- 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 the column/field configuration used to render this module's list view — display labels, sort/lock/edit capability, and redirect targets per field. Field display names are dynamically relabeled to "Material Order" for roofing-industry companies.

## Response `200`

200

- object
  - `type` 'success'
  - `data` object[]
    - `display_name` string
    - `display_key` string
    - `data_key` string
    - `field_type` string
    - `data_type` string
    - `display_type` string
    - `is_sortable` boolean
    - `is_locked` boolean
    - `allow_editing` boolean
    - `combine_with` string
    - `checked` boolean
    - `redirect` object
      - `is_enabled` boolean
      - `module` string
      - `data_key` string

## Changes

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

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