Our upstream team is transitioning RFID SKU data to a new source. During this period, there may be times when no new data is available. We’ll notify you once the new source is live.
Merchandising will be making additional hierarchy changes for Departments 5, 7, and 87 between Monday, February 23 and Friday, February 27. Additional hierarchy changes for fashion departments will begin on Monday, March 2 and last for up to 8 weeks. The above hierarchy changes will be reflected in Channel Performance on a daily basis, pulling in changes each morning from the day before. If you have any pre-built reports utilizing hierarchy filters, you may need to clear these filters and recreate them with the new hierarchies. Shopper Behavior, Customer Perception, Digital Landscapes, and Insights Activation will reflect all Departments 5, 7, and 87 hierarchy changes on Monday, March 9. Fashion hierarchy changes for Shopper Behavior, Customer Perception, Digital Landscapes, and Insights Activation will also begin to be reflected on Monday, March 9 and will continue to update on a weekly cadence each Monday.
Upcoming restatement to correct overinflated backroom inventory data Walmart Data Ventures was recently informed up our upstream partners that, due to faulty Logic, Backroom Adjustment Retail Amount metrics (backroom_adj_cst_amt and backroom_adj_retail_amt) are overinflated within Backroom Adjustment Inventory at the store level. To correct this data, Walmart Data Ventures worked with upstream partners to restate the data beginning Friday, March 6, and will finalize this work on Monday, March 9. For Data Feeds and Cloud Feeds clients, we will send the updated data in the form of insert and updates, Please plan accordingly.
API call attempts have the potential to return a variety of errors. Find common error codes, reasons, and resolution details below.
Refer to the applicable endpoint reference page for specific endpoint error information, this page is for quick reference of common errors. Expand each to view details.
400 (BAD REQUEST)
Error Message
Reason
Resolution
Invalid parameter.
An invalid parameter may have been provided in the request.
Please check and provide a valid parameter in the request header. See the individual endpoint reference page for specific parameter information.
401 (UNAUTHORIZED)
Error Message
Reason
Resolution
Could not authenticate inrequest, auth signature: Signature verification failed.
This is possibly because of: 1. using an incorrect private key for generating the signature. 2. a malfunctioning Authentication signature.
Make sure you are using the correct private key and other parameters. Please try generating a new Authentication Signature.
The Tmestamp 1639999142531 passed for the signature has expired .
The Tmestamp for the signature has expired.
Please generate a new signature and try again. Signatures expire every 3 minutes.
403 (FORBIDDEN)
Error Message
Reason
Resolution
The Consumer ID is not subscribed to the service name.
When the "wm_consumer.id" Header is not present or not correct.
Please use the provided Consumer ID in the request header.
Request is missing required security headers, please read documentation for security headers.
This is because any one of the mandatory request headers are missing.
Request headers should have all four attributes: wm_consumer.id, wm_sec.auth_signature, wm_consumer.intimesta mp, and wm_sec.key_version.
404 (NOT FOUND)
Error Message
Reason
Resolution
Not found.
The provided URL is incorrect.
Please use the correct endpoints. Refer to individual endpoint reference pages.
A requested GTIN is not mapped to the Supplier.
- A provided GTIN doesn’t belong to the supplier. - A provided GTIN is not mapped to the supplier for a few stores.
Please use the appropriate GTIN belonging to the supplier.
Data not found for the given request parameters.
There is no data for a requested GTIN and storeNbr.
Provide the valid GTIN for the particular storeNbr.
405 (METHOD NOT ALLOWED)
Error Message
Reason
Resolution
Method not allowed.
An incorrect HTTP verb has been used.
Use the correct request method. Refer to the endpoint reference pages or endpoint quick view page for relevant methods.
429 (TOO MANY REQUESTS)
Error Message
Reason
Resolution
Too many requests, please retry after some time.
This is possibly due to a number of requests exceeding the given quota. The peak rate limit for Near Real Time API is generally 600 transactions per minute (TPM). Please refer the Throttling section in the endpoint reference pages for specific endpoint information.
Since the requests are getting throttled, it is suggested to try again after some time.
500 (INTERNAL SERVER ERROR)
Error Message
Reason
Resolution
Internal server error.
One or more services are unavailable. Please contact support.
