FAQs
Here you can find answers to common Cloud Feeds questions. Can't find the answer to your question? Please contact us.
Data Feed API FAQs
Frequently asked Data Feed API questions.
What is the expiration timeline for digital signatures and timestamps?
The digital signatures and timestamps expire every 3 minutes; we recommend users regenerate the signature for every call.
Does everyone at the company need an API Consumer ID?
No, API Consumer IDs are shared at a company level. The same Consumer ID will be applicable for everyone in the company.
Does the RSA key have an expiration date?
No, the RSA key does not have an expiration date.
Can I request a different Consumer ID for production if I lose my keys?
Yes, we can regenerate the Consumer ID for production. Regeneration of Consumer IDs can take 3-5 business days.
Do I need to generate different RSA keys for Sandbox, Production, and Category Advisor APIs?
Yes. You will need to use a unique RSA key for each environment. Please refer to the table below for more details on RSA keys requested.
| Scenario | Description | Keys Needed |
|---|---|---|
| 1 | Sandbox only | 1 RSA needed |
| 2 | Production only | 2 RSAs needed: 1 for Production and 1 for Category Advisor API |
| 3 | Both Production and Sandbox | 3 RSAs needed: 1 for Sandbox, 1 for Production, and 1 for Category Advisor API |
Is there a limit to the number of API calls that can be called?
Data Feed APIs have a uniform rate limit of 25 transactions per minute (TPM) across all of the API endpoints (Snapshot, Status, History, and Incremental) that are provided to the Clients. For more info, please refer to our API Documentation.
Is there a TTL (Time to Live) for Signed URLs?
All signed URLs are activated with a TTL of 10 mins. Once this TTL expires, new sessions are not allowed, but an existing session will not be stopped while downloading files.
When will the Data Feed API data be refreshed?
SLAs will vary by feed and are listed in our API documentation.
How often is data refreshed for API consumption?
Data refresh will occur as often as the underlying data asset allows. For example, Store Sales and Store Inventory will differ in refresh rate due to the number of records being restated and the processing time of the underlying source. Our recommendation is to set up an automated process to call our "Get Status" APIs at least every 15 minutes so you will capture the latest status as soon as the data is updated.
Why am I seeing 'no data available' when I call an API?
For incremental data feeds, there may be days without new data, such as during holiday periods for some feeds or when there are no modular changes. These are valid scenarios where the API call can show a 204 Response Code where the API Call is successful, but there is no data available to be generated or where feed will not appear as "Available" in the Get Status call.
Please ensure that you have received an "Available" response from our "Get Status" API for the data feed in question. Additionally, if more than 45 days have passed since onboarding and historic data has not been ingested, you must submit a request to regenerate the historic data.
In the Order Forecast Feed, what does the value 0 in the dc nbr field denote?
The value "0" will show for Vendor to Store or Vendor to DC orders.
Please note:
The store_nbr field represents the destination to where the item needs to be shipped. In the case of Vendor to DC and DC to DC orders, this field will contain the Distribution Center Number instead of the Store number.
The dc_nbr field represents the source from where the item will be shipped. For Vendor to Store and Vendor to DC orders this field will be null.
In Order Forecast Feed, some store nbr values will contain the Distribution Center Number, while dc nbr is 0, what does this signify?
This will happen when it is a Vendor to DC order.
Please note:
The store_nbr field represents the destination to where the item needs to be shipped. In the case of Vendor to DC and DC to DC orders this field will contain the Distribution Center Number instead of the Store number.
The dc_nbr field represents the source from where the item will be shipped. For Vendor to Store and Vendor to DC orders this field will be null.
Why are some Forecast Sequence Number fcst seq nbr values other than especially when dc nbr is 0, what does it mean?
fcst_seq_nbr are unique numbers generated by the forecasting system for a given store/item combination on a given date. Please see our Business Glossary for more information on Forecast Sequence Number.
Availability Ship Date avlbl ship dt just shows one value throughout (i.e., 1970-01-01). Is this a real value?
When requesting forecasting values, you will want to use Scheduled Ship Date (sched_ship_dt) because that is used to tell when an item is scheduled to be shipped.
