Request an API traffic report
Sellers can request an API traffic report to view historical Marketplace API traffic and client‑error trends. The report breaks down calls by API endpoint and 4xx error code so you can spot integration issues and rate‑limit patterns quickly.
When to use it
- Monitor overall API call volume by endpoint.
- Identify spikes in 400/401/403/404/429 and other 4xx errors.
Request the report
- Call Create Report Request and set:
reportType=API_traffic_reportreportVersion=v1
- (Optional) Add date range filters in the request body to limit the lookback window. If you don’t pass a range, the report defaults to the past 30 days. The maximum lookback is 2 years.
- Check the request status and download the file when it’s ready.
Example (cURL)
curl --request POST \ 'https://marketplace.walmartapis.com/v3/reports/reportRequests?reportType=API_traffic_report&reportVersion=v1' \ --header 'accept: application/json' \ --header 'content-type: application/json'
# If needed, include date range filters in the request body per the On-request Reports guide.
Columns in the report
| Column | Description |
|---|---|
| API group | High-level area (for example, Orders). |
| API endpoint | Endpoint path (for example, GET /v3/orders). |
| Total API traffic | Sum of all API calls in the selected time period. |
| 400 API traffic | Sum of 400 – Bad Request calls in the selected time period. |
| 401 API traffic | Sum of 401 – Unauthorized calls in the selected time period. |
| 403 API traffic | Sum of 403 – Forbidden calls in the selected time period. |
| 404 API traffic | Sum of 404 – Not Found calls in the selected time period. |
| 429 API traffic | Sum of 429 – Too Many Requests calls in the selected time period. |
| Other 4xx API traffic | Sum of all remaining 4xx calls (other than 400, 401, 403, 404, 429) in the selected time period. |
See also
Updated 1 day ago