We are aware that Order forecast for WM Weeks 40-52 for FYE 27 and WM Weeks FYE 28 is incomplete or missing. Our Data teams are working to resolve on priority and we will share more information shortly..
Due to an ongoing issue, the availability of data assets is currently delayed. Our team is actively working to resolve the issue and restore access as quickly as possible. We appreciate your patience and understanding.
On September 18, users may experience delays in receiving Store Inventory (catman) data, potentially resulting in an SLA miss. We are aware of the delay and our team is working to resolve it. We apologize for the inconvenience.
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. 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.
Welcome to our Walmart Data Ventures API Documentation! Please note that this is the API v2 documentation. If you're looking for Direct Shipment Capture (DSC) v1 or our other NRT/Volt API offerings, please refer to our v1 Documentation.
Before You Start
Before you start setting up your access, please note the following.
New to Our APIs? Please make sure your business partners have already connected with a Walmart Data Ventures Account Manager or Sales Engineer and have submitted an onboarding request form.
Already Onboarded? If you've already onboarded to any of our API offerings (including Data Feeds, NRT, or DSC v1), please reach out to a Walmart Data Ventures Account Manager or Sales Engineer to request your client Secret so you can begin generating Bearer Tokens.
How Our Documentation is Organized
A basic understanding of the main sections of our docs can help you find what you need:
Get Started Guide This section (the section you're currently in) guides you through the steps necessary to authenticate your access using OAuth credential management. If you haven't yet set up your access, start here.
Documentation Our documentation provides endpoint details and error codes you may encounter. Once you've set up your access, go here to find details such as optional headers, parameter descriptions, and to try out our endpoints.
Release Notes Our Release Notes tell you everything you need to know about upcoming and past releases, as well as any updates to the documentation.
Disclaimer
Your use of documentation is at your own discretion and risk. To the maximum extent permitted by law, the data, documentation and all related software, components, and support are provided by Walmart on an ‘as-is’ and ‘as available’ basis without any warranties of any kind, and Walmart expressly disclaims any and all express and implied warranties, including, but not limited to, warranties of merchantability, fitness for a particular purpose, title, non-infringement, non-interference, and warranties arising from a course of dealing. You acknowledge that Walmart does not warrant that the APIs will be uninterrupted, timely, secure, or error-free. Walmart may modify and delete API documentation in its sole discretion and without notice.
In no event shall Walmart be liable to you or any third parties for any damages whatsoever, including, without limitation, those resulting from loss of use, damage to your computer system, loss of data or profits, or any liability arising out of or in connection with the use of the data, documentation, software, components, or support.
