Search item issues

Search for item-level diagnostic issues that block or limit items from being used in Search Engine Marketing (SEM). Returns paginated, item-level diagnostic details including campaign associations, issue types, severity, remediation guidance, and overall item status.
Market availability: US only

Items in SEM campaigns must meet content, quality, and policy requirements before they can be advertised on search engines (For example, Google Shopping Ads). This endpoint surfaces the specific issues preventing or limiting an item's SEM eligibility, along with actionable remediation guidance so sellers can resolve problems and restore advertising reach.

Current scope

This endpoint currently returns diagnostics for items that are part of active SEM campaigns for the authenticated seller. Each item in the response includes its campaignAssociations — the list of campaigns the item belongs to. Items not associated with any campaign are not included in the results.

Default behavior

  • When no request body is provided, defaults to offset=0, limit=100 with no filters
  • When no issueCategory filter is provided, returns only items with issues (BLOCKED or LIMITED)
  • To include healthy items, explicitly pass issueCategory filter with NO_ISSUES or all three values
  • By default, the API prioritizes returning actionable diagnostic issues rather than healthy items. This reduces payload size and improves relevance

Supported filters

Filters are combined with AND logic. Multiple values within a single filter act as OR.

Filter FieldSupported ValuesMax ValuesDescription
issuesAny valid issueType enum value100Filter by specific SEM issue types (For example, ITEM_OUT_OF_STOCK, TITLE_TOO_LONG, POLICY_VIOLATION)
issueCategoryLIMITED, BLOCKED, NO_ISSUES100Filter by SEM issue severity — BLOCKED items cannot be advertised at all, LIMITED items have reduced SEM performance
itemIdNumeric string item IDs100Filter by Walmart catalog item identifiers within the seller's active campaigns. In a future release, this filter will also support items outside of campaigns.

Response structure

Each response contains two top-level fields:

  • pagination: Standard pagination metadata including hasNextPage/hasPreviousPage for convenient UI navigation
  • data: Array of item-level diagnostics. Each item appears once per unique offerId with all campaign associations listed. Each item includes an issueCategory field representing the overall SEM eligibility status of the item, and an issues array containing issue type identifiers. Issues are item-level, not campaign-specific — a blocked item is blocked in all SEM campaigns it belongs to.

Issue metadata (name, description, fixability, help links) is not included in this response. Partners should use the dedicated GET /item-issues/issue-types endpoint to retrieve complete issue metadata and cache it locally (TTL: 24 hours).

Issue categories

CategorySEM Impact
BLOCKEDItem cannot be advertised on search engines. Must be resolved before the item can appear in SEM ads. Examples: out of stock, missing title, policy violation, invalid image.
LIMITEDItem can be advertised but with reduced visibility or performance on search engines. Resolving these issues improves ad reach and effectiveness. Examples: title too long, low image quality, description too short.
NO_ISSUESItem has no SEM issues and can be advertised normally with full visibility.

Actionable vs non-actionable issues

Each issue type has an isFixable flag available via the GET /item-issues/issue-types reference endpoint:

  • isFixable=true: Seller can fix the issue to restore SEM eligibility (For example, restock inventory, update title, fix image). Partners should surface these with a "Fix Now" UI affordance.
  • isFixable=false: Requires Walmart or system intervention (For example, Google policy violations). Partners should display these as informational — the seller cannot directly resolve them.
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Optional search request with pagination and filters.
Defaults to offset=0, limit=100 with no filters if body is absent.
When no issueCategory filter is provided, only items with issues (BLOCKED or LIMITED) are returned.
This reduces payload size and improves relevance — diagnostics API consumers typically want problems, not healthy-item confirmation.
To include all items, explicitly pass issueCategory filter with all three values: LIMITED, BLOCKED, NO_ISSUES.

Request DTO for searching item-level diagnostics.

All fields are optional. The request body itself is also optional — when absent, sensible defaults are applied:

  • page.offset: 0
  • page.limit: 100
  • No filters (returns only items with issues: BLOCKED or LIMITED)

Current scope: Results are scoped to items in active SEM campaigns. In a future release, the itemId filter will support querying any item in the seller's catalog.

Default behavior: When no issueCategory filter is provided, the API returns only items with issues (BLOCKED or LIMITED). This design decision ensures diagnostics consumers receive actionable problems first, reducing payload size and improving relevance. To include healthy items, explicitly pass issueCategory with value NO_ISSUES or use all three values.

Filter behavior: Filters are combined with AND logic. Multiple values within a single filter act as OR. For example, filtering by issueCategory=[BLOCKED, LIMITED] returns items that are either BLOCKED or LIMITED. Adding a second filter issues=[ITEM_OUT_OF_STOCK] narrows results to items that are (BLOCKED or LIMITED) AND have ITEM_OUT_OF_STOCK.

page
object

Pagination configuration for controlling result set size and navigation.

Defaults when page is not provided: offset=0, limit=100

Both offset and limit are required when the page object is provided.

filters
array of objects

List of filters to narrow down results.
Multiple filters are combined using the AND operator.
Each filter field must be specified only once (no duplicates).

filters
Headers
string
required

Access token obtained from the Token API. This is required for authenticating requests to Walmart Marketplace APIs.

string

A unique ID to identify the consumer request by channel. Use the Consumer Channel Type received during onboarding.

string
required

Specifies the name of the Walmart service being called.

string
required

A unique ID that identifies each API call and is used to track and debug issues. Use a randomly generated GUID for this ID.

string
required

Only supported Media Type : application/json.

string
required

Only supported Media Type : application/json.

Responses

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json