Skip to main content
GET
List Cases
List the support cases on your team’s orders, most recently active first. A case counts as active whenever someone posts on it or its status changes. Filter with status, reason and order_id, or pass search to match part of an order ID or case ID. Page through results with limit (up to 500) and offset. total is the number of cases that match the filters, across all pages. Each entry is a case summary without its messages. Fetch the thread with Get Case.

Case Statuses

A case’s status says whose move it is.
closed isn’t final. Replying on a closed case inside the order’s case window reopens it. See Post Case Message.
To find the open case on an order, filter by order_id and look for the entry whose status isn’t closed. There’s at most one.

Authorizations

Authorization
string
header
required

Zinc API key (Bearer zn_...)

Headers

authorization
string | null

Query Parameters

limit
integer
default:50
Required range: 1 <= x <= 500
offset
integer
default:0
Required range: x >= 0
status
enum<string> | null

Whose move it is on a support case.

Only closed is terminal, and not even that for long: a customer reply inside the open window reopens a closed case rather than starting a new one.

Available options:
open,
waiting_on_customer,
on_hold,
closed
reason
enum<string> | null

What a support case is about. Routing and reporting only — no reason triggers automation.

Available options:
not_received,
missing_item,
late,
damaged_or_wrong_item,
cancellation,
address_change,
return,
billing,
other
order_id
string<uuid> | null
search
string | null

Partial match on order ID or case ID

Maximum string length: 64

Response

Successful Response

cases
CaseSummary · object[]
required
total
integer
required