We use cookies to understand how this site is used and to improve your user experience. By using this site, you consent to the use of cookies. For more information and to learn how to manage your cookie preferences, please see our Privacy Notice.
Cloud Cache BETA

Simple, fully managed data cache

Efficiently consume messages on IEX Cloud, without having to set up your own data storage infrastructure.

Get started

We're here to help you scale

Fully Managed

No servers to manage. No databases to purchase. Cloud Cache automates data storage, scaling, high availability, monitoring, and administration.

Move Faster

We manage the complexity of data infrastructure so you can focus on building for your users, rather than spending time on server setup or optimizing your message usage.

Flexibility

Choose the right cache size to fit your cost and data requirements.

How it works

You can use Cloud Cache on any API call by passing the query parameter cache=true . If the associated URL is found in the Cache, results will be returned from the Cache. If the associated URL is not found in the Cache, it will pull data from the Cloud API and store the results in an unused Cache slot (if available).
Each unique URL takes up one cache slot. It is case insensitive and order of parameters does not matter.
Each cache slot has a customizable expiration timeframe ("Time To Live"/TTL). The default is 24 hours for most endpoints unless otherwise specified in the documentation.
Full message amount is charged only when data is not available in Cloud Cache and so is fetched from the Cloud API. Each request that is available in Cloud Cache applies a message weight of 1 for each unit, as opposed to the per unit weighting shown in our documentation under the “Data Weighting” header for an endpoint.
Batch queries count as 1 cache slot per symbol + type combination.

Worry-free caching starts at $50/mo

100 slots
$50/mo
500 slots
$150/mo
2,500 slots
$350/mo
10,000 slots
$950/mo
50,000 slots
$3,500/mo
250,000 slots
$12,500/mo
Get started

Cloud Cache Examples

Caching estimate data for AAPL, default TTL

Initial Call

Estimate is requested

https://cloud.iexapis.com/stable/stock/aapl/estimate?cache=true&token={YOUR_TOKEN}

10,000 messages used

1 cache slot is used to store the data with a default TTL

Future Call

Estimate is requested

Data is found in Cloud Cache

1 message used

Caching estimate data for AAPL, custom TTL

Initial Call

Estimate is requested

https://cloud.iexapis.com/stable/stock/aapl/estimate?cache=true&cacheTTL=172800&token={YOUR_TOKEN}

10,000 messages used

1 cache slot is used to store the data with a custom TTL of 2 days, specified in seconds (custom TTLs can be up to 30 days)

Future Call

Estimate is requested

Data is found in Cloud Cache

1 message used

Caching data with batch call

Initial Batch Call

Batch Request for AAPL and BAC last quarterly earnings and financials

https://cloud.iexapis.com/stable/stock/market/batch?cache=true&symbols=AAPL,BAC&types=financials,earnings&token={YOUR_TOKEN}

12,000 messages used

4 cache slots are used to store the data

Future Call

Last quarterly earnings and financials are requested for AAPL, BAC, and FB

https://cloud.iexapis.com/stable/stock/market/batch?cache=true&symbols=AAPL,BAC,FB&types=financials,earnings&token={YOUR_TOKEN}

Data is found in Cloud Cache for AAPL, and BAC. Most recent quarterly earnings and financial for FB pulled from Cloud API

2 messages used for data fetched from Cache. 6,000 messages used for FB data pulled from API. 2 more cache slots are used to store FB earnings and financials

Create your account.

Get started