We expect the data refresh to be delayed for ecomproductcontentscore dataset today (2026-06-17). We are actively working to resolve the issue and apologize for the inconvenience.
We have become aware that there is missing data for June 2, 2026 within our headless access Channel Performance solutions. 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 2:00 pm CT this morning (6/3/26). Please see the next steps below on how to restore missing data. The data has been restated and published as an on-demand update in the status table. Suppliers could have manually used the status timestamp to read the restated store sales data using CDF on June 3. If they did not take manual action, then it processed automatically on June 4 via the normal CDF process.
We have become aware that there is missing data for June 2, 2026 within our headless access Channel Performance solutions. 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 2:00 pm CT this morning (6/3/26). Please see the next steps below on how to restore missing data. For the affected tables, we will be processing the data in our incremental on 6/4. We will provide “U” updates for the incorrect data and "I" for the new records that weren't sent.
We have become aware that there is missing data for June 2, 2026 within our headless access Channel Performance solutions. 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 2:00 pm CT this morning (6/3/26). Please see the next steps below on how to restore missing data. For the affected tables, we will be processing the incremental data on 6/4. We will provide “U” updates for the incorrect data and "I" for the new records that weren't sent.
We are aware of a data issue with RFID Tag Part table. We are working to fix the issue.
Service Advisory: Cloud Feeds Pipeline Delay We are currently experiencing an infrastructure issue impacting Cloud 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.
The Associations API provides Preferred Service Providers (PSPs) near real-time visibility into which supplier data they have permission to access.
GET
/cp/reference-apis/v1/associations
Response Details
Parameter
Description
Data Type
company_name
The name of the supplier.
string
wm_context_identifier
A Walmart Supplier's unique identifier.
string
Error Codes
Find common Associations API error codes, reasons, and resolution details below.
Error Code
Error Message
Reason
Resolution
400
No associations data is present for psp supplier.
The PSP is not associated with any Charter Supplier.
Make sure you have a signed TPA with a supplier.
400
wm_consumer.id does not belong to a psp.
The WM_CONSUMER.ID header provided is not valid.
Please check the provided WM_CONSUMER.ID and try again.
Disclaimer
Your use of the API documentation is at your own discretion and risk. To the maximum extent permitted by law, the APIs, 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, noninfringement, 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 APIs, documentation, software, components, or support.
