Parity between Scintilla Channel Performance & Merch One Scintilla’s Store Inventory metrics are transitioning from a legacy data source to a new Enterprise Inventory (EI) data source to align with the enterprise-standard inventory system, eliminate inconsistent logic within the legacy data source, and improve replenishment metric accuracy. This transition will occur by August (exact date TBD). Merchandising transitioned Merch One to this new data source on Tuesday, June 23. As a result, there will be some variance when comparing data between Scintilla and Merch One from June 23 – until Scintilla makes the same transition for the following metrics: Store (out of stock metrics), Total On Hand, Total In Transit, Total In Warehouse, Total On Order. A new banner will be raised when this work is completed.
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.
API call attempts have the potential to return a variety of errors. Here you can find the most common errors, their possible reasons, and how to resolve them. If you encounter an error that you are unable to resolve, please note as much detail as possible and contact us for assistance.
Find common error codes, reasons, and resolution details below. Expand each to view details.
204 (NO CONTENT)
Error Message
Reason
Resolution
Empty body.
No data is available for the request.
- For Post requests: please change the feed Date input and retry the request. The feed Date should not be greater than 30 days. - For Get requests: There is no data available for the current Date. Please check the availability using the Status API before calling to avoid this error. - For Status API: Please be sure to call the Status API on Sundays after 5:00 AM CST to check the availability status of feed files. This ensures that all necessary refreshes and feed generations are completed. Calling before this time could result in a 204 (No Content) error from the Status API.
400 (BAD REQUEST)
Error Message
Reason
Resolution
FeedDate not allowed for history feed type.
The feed Date should not be passed with POST History endpoints.
POST History endpoints only accepts "fileNames" as an input parameter in the request body. Please remove the parameter.
FeedDate is a required field.
Feed Date is mandatory for POST Incremental and Status endpoints.
Please pass "feedDate" as an input parameter in the POST endpoint request body.
401 (UNAUTHORIZED)
Error Message
Reason
Resolution
The timestamp passed for the signature has expired.
The Authorization Signature timestamp has expired for the request header "wm_consumer.intimestamp".
Please generate the new signature and pass it in the request header.
IAM Exception: IAM-1000: Signature length not correct: got 258 but was expecting 256.
An invalid Authorization Signature was provided in the header field "WM_SEC.AUTH_SIGNATURE".
Please generate a new signature and pass it in the request header.
Could not authenticate in-request. Authorization Signature: Signature verification failed.
This could be caused by: 1. using the incorrect private key when generating the signature /or/ 2. an Authorization Signature malfunction.
Please make sure you are using the correct private key and other parameters. If necessary, please generate a new Authorization Signature.
403 (FORBIDDEN)
Error Message
Reason
Resolution
The consumer id **** is not subscribed to the service name.
Occurs when the "wm_consumer.id" header is not present in the request header. Also occurs when "wm_consumer.id" is either null or incorrect.
Please check your Walmart provided Consumer ID and pass the correct Consumer ID in the request header.
Request is missing required security headers, please read documentation for security headers.
Occurs when the required mandatory headers are not passed with the request.
The mandatory request headers with api proxy are: 1. wm_consumer.id 2. wm_sec.auth_signature 3. wm_consumer.intimestamp 4. wm_sec.key_version Please pass all mandatory headers in the request.
Unable to retrieve service related information, please read documentation for mandatory headers or URL specification.
Occurs with an invalid api proxy url.
Please provide a valid api proxy url.
You are not authorized to call this API.
Occurs with an invalid api proxy url.
Please provide a valid api proxy url.
404 (NOT FOUND)
Error Message
Reason
Resolution
Not found.
The provided URL is incorrect.
Please check the documentation for the correct endpoints (see API Reference pages) and retry the request.
405 (METHOD NOT ALLOWED)
Error Message
Reason
Resolution
Method not allowed.
An incorrect HTTP verb has been used.
Please check the documentation for the correct endpoints (see API Reference pages) and retry the request.
406 (NOT ACCEPTABLE)
Error Message
Reason
Resolution
Please provide a valid api url.
This could occur because: 1. an incorrect endpoint was passed /or/ 2. a Post request was passed as a Get request.
Please recheck the documentation (see API Reference pages) and provide a valid request type and endpoint.
429 (TOO MANY REQUESTS)
Error Message
Reason
Resolution
Too many requests, please wait and retry after some time.
Occurs when the number of requests has exceeded the given quota Throttling for details).
Please limit calls to the 25 transactions per minute (TPM) maximum.
500 (INTERNAL SERVER ERROR)
Error Message
Reason
Resolution
Internal server error.
One or more services are unavailable. Please contact support.
