One API, one response format
Every endpoint of the fxapi foreign exchange rates API shares the same conventions: authenticate with the apikey header, choose any of the 190+ currencies as base_currency, limit the response with currencies or type, and read values keyed by currency code (data.{CODE} for latest, historical, convert and fluctuation). Learn the pattern once and every feature above works the same way.
| Feature | Endpoint | Free | Basic | Professional | Enterprise |
|---|---|---|---|---|---|
| Latest rates | /v1/latest | daily | hourly | every 60 s | every 60 s |
| Historical rates | /v1/historical | ✓ | ✓ | ✓ | ✓ |
| Fluctuation | /v1/fluctuation | ✓ | ✓ | ✓ | ✓ |
| Averages | /v1/average | ✓ | ✓ | ✓ | ✓ |
| Conversion | /v1/convert | – | ✓ | ✓ | ✓ |
| Time series | /v1/range | – | – | ✓ | ✓ |
| Requests / month | 300 | 15,000 | 600,000 | 1,700,000 |
Crypto and precious metals are included on every plan – see the crypto exchange rates API and the gold and silver price API. AI agents can call every endpoint through the hosted MCP server. Compare plans on the pricing page or start with the free exchange rate API.
Frequently asked questions
Which fxapi features are included in the free plan?
Latest rates (updated daily), historical rates since 1999, fluctuation, monthly/quarterly/yearly averages, the currency list and the status endpoint – 300 requests a month.
Do all endpoints use the same response format?
Yes. Every endpoint accepts
base_currency, currencies and type, and values are keyed by currency code – under data.{CODE} for latest, historical, convert and fluctuation, and per timestamp or period for range and average. Range, fluctuation and average can also return CSV.Where is the full API reference?
In the documentation and the machine-readable OpenAPI 3.1 spec.