There is delay in data refresh for ecom prod content quality score data. Our team is actively working to resolve the issue as quickly as possible.
We appreciate your patience and understanding.
Hierarchy changes are now reflected across the Data Access and Collaboration portfolio. If you have any pre-built reports utilizing hierarchy filters, you may need to clear these filters and recreate them with the new hierarchies.
Please submit requests via a support ticket to get historical UPC Sales to reflect hierarchy changes in Shopper Behavior. You can submit a ticket for these August changes beginning on Monday, August 24.
Hierarchy changes are now reflected across the Data Access and Collaboration portfolio.
Please submit requests via a support ticket to get the updated item hierarchy. You can submit a ticket for these August changes on or after Tuesday, August 11.
We will restate corrected Markup Markdown Board data this weekend. The restated records will flow through incremental updates to both Data Feeds and Cloud Feeds, which may update values previously received. Please ensure downstream processes are prepared to consume these incrementals. We will update this notice when the restatement is complete.
We are aware of a data issue with RFID Tag Part table. We are working to fix the issue.
Service Advisory: Cloud Feeds, Data feeds Pipeline Delay We are currently experiencing an infrastructure issue impacting Cloud Feeds and Data feeds data pipelines due to a constraint within our platform. As a result, there may be delays in data availability and refreshes. We are actively engaging and working toward resolution. We will provide updates as additional information becomes available.
We have become aware that there is missing store sales data for May 26, 2026. This missing data is impacting Scintilla suppliers and the category advisor persona who rely on headless access (Cloud Feeds, Data Feeds API and Scintilla Media Data Feed). Our team investigated the issue and resolved it as of 11:30 am CT this morning. Report Builder is unaffected and has all sales data for May 26, 2026. Please see the next steps below on how to restore missing sales data. Data Feeds API: The historical file for the affected May 26 store sales data will be made available, and suppliers will need to manually consume it to recover the missing records.
We have become aware that there is missing store sales data for May 26, 2026. This missing data is impacting Scintilla suppliers and the category advisor persona who rely on headless access (Cloud Feeds, Data Feeds API and Scintilla Media Data Feed). Our team investigated the issue and resolved it as of 11:30 am CT this morning. Report Builder is unaffected and has all sales data for May 26, 2026. Please see the next steps below on how to restore missing sales data. Cloud Feeds: The data will be restated and published as an on-demand update in the status table. Suppliers can manually use the status timestamp to read the restated store sales data using CDF. If they do not take manual action today, then it will process automatically tomorrow via the normal CDF process.
Our APIs are deployed in isolated Sandbox and Production environments. Onboarding onto these environments requires that you authenticate your access with the Walmart API Proxy/Gateway before initiating an API call.
🚧
Already Onboarded to Our APIs?
If you've already onboarded to any of our API offerings (including Data Feeds, NRT, or DSC v1), you do not need to generate keys again - please reach out to a Walmart Data Ventures Account Manager to request your client Secret so you can begin generating Bearer Tokens.
Getting Started
The first step to authenticating your access is to generate API access keys.
Before you begin:
Before you begin generating your API access keys:
Please make sure your business partners have already connected with a Walmart Data Ventures Account Manager and have submitted an onboarding request form.
You need to have access to a command line terminal. For Windows systems, ensure that either Git Bash or OpenSSL for Windows has been installed.
Please note:
You will use your generated public key to obtain a Client ID (Walmart Consumer ID). Client IDs are shared at a company level, so the same Client ID will be applicable for everyone in the company.
Repeat the key generation steps for each environment you wish to gain access to, as outlined below:
Scenario
Description
Keys Needed
1
Sandbox only
1 Key needed
2
Both Production and Sandbox
2 Keys needed: 1 for Sandbox, 1 for Production
There are slightly different methods for generating keys, depending on whether you are using a Unix-based or Windows system.
To generate your key, select your operating system.