Starting July 15 2021, we’re making three updates to our billing – including changes to data weights and packages’ pricing.

For most of our customers, we expect that these updates will have minimal impact on your monthly costs – and for many use cases, will also help you save credits.

This guide helps answers FAQs and provides additional background information about these updates.

What’s changing?

1) We’re adjusting several endpoints’ data weights – including significantly more affordable data weights for frequently used endpoints.

On July 15, we’ll lower the cost for 31 datasets. For instance, our Historical Forex endpoint will be reduced from 100,000 to 10 credits per API call. This is made possible by the other two changes you’ll read about below.

Note that for a small handful of endpoints, there are slight increases in data weights. See the full list of data weight changes below.

2) Across the platform, each API request will use an additional one credit per call.

For instance, if the data weight for an endpoint is 100 credits per request, each API call would use a total of 101 credits. If you’re streaming data, you would use one additional credit per connection.

This one credit covers our operational costs for delivering data, and enables us to lower the cost across dozens of endpoints. Furthermore, sandbox API calls will continue to be totally free and unlimited.

3) We’re rounding out the monthly cost per package by $1.

Our Individual plan packages will cost $10 per month, and our Business plan packages will cost $30 per month. If you are purchasing or renewing packages next month, you’ll see this small change in cost.

Again, this change helps us lower the data weights across a wide range of our most popular endpoints.

Frequently Asked Questions

Which endpoints will have data weight changes?

Because of these updates, we’re able to lower the data weight for over 30 frequently used endpoints:

  • Historical News: From 5,000 to 100 credits

  • Financials as Reported: From 5,000 to 1,000 credits

  • Advanced Fundamentals: From 75,000 to 30,000 credits

  • Forex Real-time Streaming: From 500 to 10 credits

  • Forex Latest Currency Rate: From 500 to 10 credits

  • Forex Currency Conversion: From 500 to 10 credits

  • Forex Historical Daily: From 100,000 to 10 credits

  • End-of-Day Options V2: From 1,000 credits per symbol per date to 10 credits per record

  • Daily Treasury Rates: From 100 to 10 credits

  • All Commodities Endpoints: From 1,000 to 10 credits

  • All Economic Data Endpoints: From 1,000 to 10 credits

Note that a handful of endpoints will have increases in data weights. See below:

  • Company: From 1 to 10 credits

  • News: From 1 to 100 credits

  • Streaming News: From 1 to 100 credits

Note that our Historical News endpoint now has a data weight of only 100 credits rather than 5,000. See below for tips on how to most effectively use your credits.

How can I most effectively use my credits?

We offer a variety of ways to use the system more efficiently.

  • You can use batch requests to query for multiple datasets and symbols in one API call.

  • We offer Cloud Cache as a free product to Individual and Business plans that helps reduce data costs by automatically tracking the API calls that you make, and reducing the data weight when requesting the same data more than once. Learn more on our blog.

  • We also offer streaming for some datasets to all paid users. Streaming allows for continuous data updates without incurring an API call charge per update. Rather than spending one extra credit for every single API call, you’ll only use one credit per connection. For instance, you can stream stock prices rather than making individual calls to our Quote endpoint.

  • You also use Rules Engine to "subscribe" to data updates. You can set a rule with Rules Engine that sends you data anytime certain conditions are fulfilled - such as a stock price hitting a certain value, or when a certain company pays a dividend. Rather than pulling that data manually and checking for certain events or trends occurring, you can have Rules Engine screen across datasets and send the specific data you're looking for right to you.

Why is there an additional one credit per API call?

This one credit covers our operational costs for delivering data, and enables us to lower the cost across dozens of endpoints. This also allows us to continue investing in scalable infrastructure.

For most users, we anticipate that this change will add minimal cost – a few cents to a few dollars per month in usage. For instance, if you make one million API calls per month, this update would add roughly $1 per month in credit usage.

What about sandbox API calls?

Sandbox API calls are free and unlimited, and do not use any of your monthly credit allocation.

Sandbox API calls can also be used to help show how many credits would be used if that same API call were performed in production. You’ll see this one credit reflected in “sandbox data weight” that’s returned in the API request’s response header to help you accurately estimate how many credits you would use.

Which API requests use an additional credit per call?

Every production API call across the platform will use one additional credit. This includes:

  • Core Data and Reference Data.

  • Premium Data. (The additional credit used will be a core credit, rather than a Premium Data credit.)

  • Add-ons such as Rules Engines, the Excel plug-in, and Stock Price Widgets.

This does NOT include:

  • Every SSE streaming or Firehose update. Streaming will use one additional credit per connection made – not per update.

  • Sandbox API calls.

How does this work with Cloud Cache?

Cloud Cache keeps track of the API calls you’ve already made, so if you make the same request twice, you only pay a data weight of one credit rather than the full data weight.

This one credit is added on top of the one credit data weight provided by Cloud Cache. So if Cloud Cache returned data to you for one credit, you would use two credits total.

Other questions? Please don't hesitate to reach out to us at

Did this answer your question?