Skip to main content
GET /v5/shipment/list/ searches your Shipments and returns each match’s key information plus its latest event. For a single Shipment’s full record, use Retrieve Shipment Details. All parameters: API reference.

The date range is required

Every request must include exactly one of these pairs — they cannot be combined:
  • created_date_from + created_date_to
  • updated_date_from + updated_date_to
  • latest_event_date_from + latest_event_date_to
Rules: both ends together, _from_to, format yyyy-mm-ddThh:mm:ss (processed as UTC), and _from at most 13 months in the past — Perform.AI’s search retention window.

Filters and AND/OR conditions

Filters include identifiers and references, carrier_id / carrier_reference, status, current_phase, tags, notification contacts, from_country_code / to_country_code, issue_state, issue_types, and shipping_type — the reference lists them all with their limits. Most filters accept AND/OR bracket syntax. String values must be quoted, and one bracket level means AND while two mean OR:
Unquoted string values inside brackets are not parsed — the filter is silently ignored. Depending on your HTTP client, URL-encode [, ], and '.

Pagination

Pagination is cursor-based:
  1. First request: next_page=0 (or omit it). limit is 25–100, default 25.
  2. Each response returns a next_page cursor — pass it into the next request unchanged.
  3. You’re on the last page when the response no longer contains next_page.
total_result reports the total match count on every page.

Read the response

A valid search with zero matches returns HTTP 404 with api_response "4041" — not an empty array. Treat it as “no shipments matched”, not as a failure. (Document, label, PUDO, and carrier-config listings behave differently and return 200 with empty data.)

Common validation failures

Next steps