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.
Our APIs are deployed in isolated Sandbox and Production environments. Charter Supplier onboarding onto these environments requires authentication with the Walmart API Proxy/Gateway before initiating an API call. The first step to authenticating your access is generating your 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.
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.
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. PuttyGen tool is not recommended as the default format is not PKCS8.
Generating API Keys - Windows-based Systems
Watch the video or continue reading below to generate your keys.
Create a desktop folder, titled "RSA Keys" (optional)
Right-click the folder and select "Show more options" to open the Git Bash or OpenSSL terminal (optional)
From the terminal command line, you will generate an RSA key-pair:
Paste the following command into the terminal and hit enter.
Using -des3 ensures that the pem file generated in the above step will be passphrase protected. You will be prompted for the passphrase. The passphrase will be located directly above the prompt in the terminal. In the example below, 65537 is the passphrase: Example:
e is 65537 (0x010001)
Enter pass phrase for my_rsa_key_pair:
Note: Please note this passphrase in a safe location. You will use it again.
Type the passphrase into the terminal where prompted (note that while entering the passphrase, it will not look like you are actually typing) and hit enter.
You may be prompted to enter the passphrase twice.
Next, you will export the private key in the private_key.pem file:
Paste the following command into the terminal and hit enter.
Type the same passphrase into the terminal where prompted (note that while entering the passphrase, it will not look like you are actually typing) and hit enter.
Note: Keep your private key safe. You will not share your private key.
Finally, you will export the public key in the public_key.pem file:
Paste the following command into the terminal and hit enter.
Type the same passphrase into the terminal where prompted (note that while entering the passphrase, it will not look like you are actually typing) and hit enter.
What Happens Next
You should now have your public_key.pem file.
If you are requesting access to multiple environments, remember to repeat the above steps for each environment you are requesting.
Once you have your key(s), you will be able to move on to Step 2.