Currencies API Pricing Use Cases
Sample pricing simulations to help estimate Currencies API usage across REST and WebSocket usage patterns.
Currencies API Pricing Use Cases
These use cases show how Currencies API pricing can be estimated across common REST and WebSocket usage patterns.
Each example is based on a specific scenario to help customers understand rate usage, Usage Credits, Pay As You Go pricing, committed plans, and overages.
These examples are pricing simulations only. Actual usage may vary depending on the number of currency pairs, endpoint used, polling frequency, WebSocket update interval, number of connections, retries, and daily usage volume.
Before using these estimates
Currencies API usage is measured in rates.
A rate is a single exchange rate price for a specific currency pair, such as EUR/USD or USD/JPY.
One REST API response can return multiple rates. For example, requesting USD against EUR, GBP, and JPY 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 currency 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 currency 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.