If you need Walmart category data for Marketplace item setup, use Walmart’s authenticated taxonomy APIs rather than scraping pages. The right endpoint depends on whether you need the Product Type hierarchy, the older category taxonomy, or categories tied to a specific item-spec feed and version. Walmart’s official integration documentation does not establish permission or a reliable method for scraping consumer-facing Walmart.com category pages; do not treat Marketplace API access as authorization to collect retail-site data.
First, identify which Walmart category data you need
“Walmart categories” can refer to distinct data. The Marketplace taxonomy API supports item setup and maintenance; it is not documented as a feed of all Walmart.com browse categories or retail product listings.
| Need | Documented path | What it represents |
|---|---|---|
| Current Product Type structure for Marketplace item workflows | GET /v3/items/taxonomy with a supported version |
Category → Product Type Group (PTG) → Product Type (PT) |
| Legacy Marketplace category structure | GET /v3/items/taxonomy without the version parameter, in the US Marketplace reference |
The older category-based taxonomy |
| Categories for a particular item-spec feed/version | GET /v3/utilities/taxonomy with the corresponding feed type and version |
Categories and subcategories, or the Product Type hierarchy, according to the selected spec |
| Public consumer browse categories or product listings | Not established by the Marketplace taxonomy documentation | Review applicable Walmart terms and obtain appropriate permission before automated collection |
Walmart’s global Marketplace reference documents the same item taxonomy endpoint and describes feed types including us, ca, mx, and cl. Required headers, market context, and version behavior can differ; check the reference for the program you use rather than assuming the US request applies globally. US Marketplace taxonomy reference · Global Marketplace taxonomy reference
Choose the appropriate taxonomy endpoint
Marketplace taxonomy: Product Types or legacy categories
For the US Marketplace item taxonomy endpoint, Walmart documents that supplying a supported version requests Product Type taxonomy; omitting it selects the legacy category-based taxonomy. The Product Type structure nests Product Types within Product Type Groups, which sit within categories. The US reference lists Product Type version 5.0 and says US supports 4.x and 5.x versions. Verify the current reference before fixing a version in an integration, since supported versions can change. US Marketplace taxonomy reference
Free tools Windows power users keep installed
One-click scans. No signup required.
Taxonomy for an item-spec feed
Use GET /v3/utilities/taxonomy when your goal is to align category choices with an item-spec feed and its version. Walmart’s utilities reference maps feed types to supported versions. The returned form can be category → PTG → PT, or category → subcategory with subCategoryId values, depending on the applicable item-spec version. This endpoint is not interchangeable with every mode of the general item taxonomy endpoint. Taxonomy by item-spec reference · Taxonomy by item-spec guide
Supplier integration
Supplier documentation also describes GET /v3/items/taxonomy, but supplier release version identifiers are time-sensitive. Its listed version 5.0.20260803-17_50_56 is associated with the September 2026 Item Setup and Maintenance API release, and 5.0.20260304-22_45_32 with the April 2026 release. Treat these as release-specific identifiers, not values to copy blindly into a different program or future integration. Check the current supplier reference for the supported version. Supplier taxonomy reference
Prepare authorized API access
These are integration APIs, not anonymous category-page endpoints. Walmart’s item-management guidance calls for program credentials and an access token, Walmart request headers, and a unique correlation ID. The exact header set depends on endpoint and program context, so use the current endpoint reference alongside the item-management authentication instructions. Marketplace item management overview · US Marketplace taxonomy reference
- Confirm your program. Determine whether your integration is US Marketplace, Global Marketplace, or Supplier.
- Choose the hierarchy. Decide whether the application needs Product Types, legacy categories, or the category/subcategory structure for an item-spec version.
- Check the current reference. Confirm the endpoint, market or feed type, version, access-token requirements, and required headers for that program.
- Request and retain the response. Preserve returned identifiers and hierarchy together with the market/feed and taxonomy version that produced them.
- Keep mappings current. Recheck supported versions and mappings when Walmart publishes integration updates.
Make a taxonomy request
The Walmart endpoint references linked above establish the endpoints and authentication requirements, but do not provide a complete, universal set of credentials, token-exchange parameters, or request-header values. Those vary by program and must come from Walmart’s current documentation. The following is therefore a request pattern, not a drop-in authenticated script: replace the placeholders with values and headers required by your program. Do not send a request without valid credentials and the required headers.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesProduct Type taxonomy request pattern
curl -X GET 'https://marketplace.walmartapis.com/v3/items/taxonomy?version=5.0'
-H 'WM_SEC.ACCESS_TOKEN: YOUR_ACCESS_TOKEN'
-H 'WM_QOS.CORRELATION_ID: YOUR_UNIQUE_CORRELATION_ID'
-H 'WM_SVC.NAME: YOUR_SERVICE_NAME'
-H 'Accept: application/json'Use version=5.0 only when that version is supported for your US Marketplace integration at the time of the request. The header names shown illustrate commonly relevant Marketplace request context; consult Walmart’s current endpoint instructions for the exact required values and any additional headers. To request the US legacy category taxonomy, omit the version parameter as specified in the US reference.
Item-spec taxonomy request pattern
curl -X GET 'https://marketplace.walmartapis.com/v3/utilities/taxonomy?feedType=YOUR_FEED_TYPE&version=YOUR_ITEM_SPEC_VERSION'
-H 'WM_SEC.ACCESS_TOKEN: YOUR_ACCESS_TOKEN'
-H 'WM_QOS.CORRELATION_ID: YOUR_UNIQUE_CORRELATION_ID'
-H 'WM_SVC.NAME: YOUR_SERVICE_NAME'
-H 'Accept: application/json'Use only a feed type/version pairing that Walmart supports for your integration. The exact query parameter requirements and headers should be confirmed in the current utilities endpoint reference.
Parse and store the hierarchy safely
Do not treat category labels as durable identifiers or flatten the response into a list of names if a later item workflow needs the parent-child relationships. Store the response’s IDs and nesting, along with enough context to identify where it came from.
- Keep the hierarchy. Preserve category → PTG → PT nesting where the Product Type response supplies it. In an item-spec result that uses categories and subcategories, retain each
subCategoryIdwith its parent category. - Version every snapshot. Record the program, market or feed type, taxonomy/item-spec version, retrieval time, and raw response. This makes changes and stale mappings diagnosable.
- Use returned IDs in workflows. Use the identifiers and structure Walmart returns for the matching item setup path rather than reconstructing IDs from displayed names.
- Refresh deliberately. Compare a newly retrieved response with the stored snapshot when changing supported versions or responding to Walmart API releases; avoid assuming that an older mapping remains valid.
What this API does not establish about scraping Walmart.com
The cited Marketplace and supplier materials document authenticated taxonomy retrieval for integration and item placement. They do not establish that the API returns every consumer-facing browse category, nor that its credentials authorize automated collection from Walmart.com retail pages. They also do not answer whether automated collection of those public pages is permitted. Review Walmart’s current terms and obtain permission applicable to your intended collection and use before building a consumer-site scraper; do not infer permission from access to a seller or supplier API.
Recommended Free Tools
Or skip the browser setup
If your actual task is to capture how a category page appears in a browser, rather than obtain Marketplace item taxonomy, ScreenshotNeo offers a one-request screenshot API. It is not a replacement for Walmart’s taxonomy API or permission to collect Walmart.com data.
Rank #4
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://www.walmart.com/cp/electronics/3944 -o shot.webpSee the ScreenshotNeo API documentation for request options. Before capture, it accepts cookie/consent banners like a visitor and removes 60+ known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers indicate the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots.
Learn about ScreenshotNeo or sign up for 1,000 free screenshots a month with no card.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting
Authentication or request rejected
Check that you created an access token for the correct program, that it is valid, and that the request includes the headers required by that endpoint. Marketplace and supplier documentation may differ; a token or header set intended for one context should not be assumed to work in another.
Unsupported version or feed pairing
For item-spec taxonomy, verify that the feed type and version are a supported pair in the utilities reference. For the US item taxonomy endpoint, confirm that the requested Product Type version remains supported. If you intend to request legacy US categories, remove the version parameter; including a Product Type version requests the newer hierarchy instead.
Unexpected hierarchy
First confirm which endpoint and mode you called. The item taxonomy endpoint with a supported version returns Product Type taxonomy; without a version, the US reference specifies legacy category taxonomy. The utilities endpoint follows the item-spec feed/version and may return categories with subcategories rather than the general taxonomy shape.
Category missing from the result
Confirm the market or feed and version match the item workflow. A taxonomy response is not evidence that all consumer browse categories or retail listings are available through that request. Check the matching current Walmart reference before treating an absent entry as an API defect.
Mappings changed after an update
Compare the current response with the saved snapshot, including IDs and parent relationships, and verify the release/version context. Supplier taxonomy identifiers are especially release-specific; check the current supplier reference rather than relying on a previously copied value.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →FAQ
Can I use the Marketplace taxonomy endpoint without an access token?
The integration guidance describes OAuth-style access-token use and required Walmart headers. The documented workflow is authenticated, not anonymous.
Does a Marketplace taxonomy response include Walmart product listings?
The cited taxonomy references describe category and Product Type structures for item workflows; they do not establish that the response includes consumer product listings.
Can I use the global taxonomy endpoint for a US integration?
Global documentation lists multiple feed types and has context-specific version and header details. Confirm the endpoint and request requirements for your actual program and market rather than substituting references by assumption.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
