Exchange Rates API Pricing Use Cases
Sample pricing simulations to help estimate Exchange Rates API usage across REST and WebSocket usage patterns.
Exchange Rates API Pricing Use Cases
These use cases show how Exchange Rates API pricing can be estimated across different usage patterns, including REST latest rates, REST historical rates, and WebSocket streaming.
Each example is based on a specific scenario to help customers understand how rate usage, Usage Credits, Pay As You Go pricing, committed plans, and overages may affect the total estimated cost.
These examples are pricing simulations only. Actual usage may vary depending on the number of asset pairs, endpoint used, polling frequency, WebSocket update interval, number of connections, and daily usage volume.
Before using these estimates
Exchange Rates API usage is measured in rates.
A rate is a single exchange rate price for a specific asset pair, such as BTC/USD or ETH/EUR.
One REST API response can return multiple rates. For example, requesting BTC against USD, EUR, and USDT returns three rates.
Historical OHLCV or time-series data is also billed by rate count. For example, one year of 1DAY historical data for one asset pair is billed as 365 rates.
How to read the examples
Each use case includes:
- The protocol used, such as REST or WebSocket
- The endpoint pattern
- The asset pairs requested
- The estimated number of rates per day
- A Pay As You Go estimate
- A comparison across committed usage plans
- Caveats that may affect real-world usage
For a general explanation of Usage Credits, committed plans, and overage billing, see the Usage Credits billing guide.
Import Data to Google Sheets/Excel
Learn how to extract market data in CSV format and import it into spreadsheet applications like Microsoft Excel and Google Sheets.
Use Case: REST Historical Daily Exchange Rates for Reporting
A sample Exchange Rates API pricing simulation for downloading one year of historical daily rates for multiple asset pairs.