Use report filters

Learn how to refine report requests with filters. Filters help you limit results to the specific data you need, reducing file size and improving performance.

Available filter types

Reports may support different filters, such as:

Date range – limit results to a specific period (for example, startDate and endDate).
Identifiers – restrict output to a set of SKUs, item IDs, or order IDs.
Status values – request only orders, returns, or items with specific statuses.
Fulfillment options – filter by ship node, shipping program, or lag time.

Check the report types page for which filters each report supports.

Default behavior

If you do not pass filters:

The API returns the full data set for the report type.
Large reports may take longer to generate and may be split into multiple files.
Some reports require at least one filter (for example, a date range). If omitted, the request fails with a validation error.

Validation rules

Filters must match supported fields for the report type. Unknown keys are rejected.
Date filters require ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDThh:mm:ssZ).
Lists (for example, SKUs) must not exceed 500 values per request.
Invalid combinations return a 400 Bad Request error.

Example: valid filter usage

POST https://marketplace.walmartapis.com/v3/reports/requests
Authorization: Bearer <access_token>
Content-Type: application/json { "reportType": "ITEM_PERFORMANCE", "filters": { "sku": ["SKU123", "SKU456"], "startDate": "2025-08-01", "endDate": "2025-08-31" }
}

Example: invalid filter usage

POST https://marketplace.walmartapis.com/v3/reports/requests
Authorization: Bearer <access_token>
Content-Type: application/json { "reportType": "ITEM_PERFORMANCE", "filters": { "invalidField": "XYZ", "startDate": "08-01-2025" }
}

Response

{ "errors": [ { "code": "INVALID_FILTER", "message": "invalidField is not a supported filter for ITEM_PERFORMANCE" }, { "code": "INVALID_DATE", "message": "startDate must be in ISO 8601 format" } ]
}

Next steps

Updated 3 days ago