Batch calls will have an additional 1 credit charge for the entire batch, regardless of the number of symbols or channels contained in the batch. SSE connections will have a 1 credit charge on initial connection, not per record. Calls that result in 4XX or 5XX error codes.Timeseries Metadata and Inventory endpoints.This allows us to keep data costs lower across a wide variety of datasets. Other credits and debits API UseĪll API calls will have an additional 1 credit access charge. You can also track this information in the console. API calls will return iexcloud-credits-used in the header to indicate the total number of credits consumed for the call, as well as an iexcloud-premium-credits-used to indicate the total number of premium credits consumed for the call.
#Apple sandbox cloud upgrade#
If the sum of these charges exceeds your monthly credit allocation, you will need to upgrade or purchase additional packages to continue accessing data.Ĭredit allocations reset on the first of each month at 00:00:00 UTC. Each endpoint has its own weight which you can find in the documentation below. If you don’t receive any records, you won’t be charged for accessing that dataset. When you access a dataset, the total weight charged for the access will generally be the weight multiplied by the number of records received (taking into account the other possible credits or debits below). We call this associated credit cost the dataset’s weight. How much does it cost to distribute the data? With billions of API calls and bursty workloads around market hours, our infrastructure needs to scale up and down to ensure constant uptime and consistent delivery.Ingesting and normalizing data has infrastructural costs on top of the base dataset cost. How much does it cost to acquire the data? Some datasets we collect on our own, other datasets we purchase from upstream vendors.
#Apple sandbox cloud update#