Exchange Rate is a simple tool for getting the current exchange rate between two currencies. It returns the current exchange rate.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Exchange Rate response payload
}
}
About the Exchange Rate API
Exchange Rate works by analyzing the data provided and returning the current exchange rate between two currencies. It uses various sources to determine the data and returns the current exchange rate.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Exchange Rate
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Exchange Rate API do?
How do I authenticate Exchange Rate API requests?
How much does the Exchange Rate API cost?
How fast is the Exchange Rate API?
What response formats does the Exchange Rate API support?
What HTTP method does the Exchange Rate API use?
Request parameters — GET /v1/exchangerate
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
currency1Required | string | USD | The first currency you want to get the exchange rate for |
currency2Required | string | EUR | The second currency you want to get the exchange rate for |
curl "https://api.apiverve.com/v1/exchangerate?currency1=USD¤cy2=EUR" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/exchangerate
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"currency1": "USD",
"currency2": "EUR",
"exchangeRate": "0.851223",
"inverseRate": "1.174773"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
currency1 | string | "USD" | The first currency code requested for exchange rate |
currency2 | string | "EUR" | The second currency code requested for exchange rate |
exchangeRate | string | "0.851223" | The current exchange rate from currency1 to currency2 |
inverseRatePremium | string | "1.174773" | The inverse exchange rate from currency2 to currency1 |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Exchange Rate calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/exchangerate
No SDK to install — this is a plain HTTPS call to /v1/exchangerate with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/exchangerate" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/exchangerate
Install the Node.js SDK, then call the Exchange Rate API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/exchangerateconst res = await fetch("https://api.apiverve.com/v1/exchangerate", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/exchangerate
No SDK to install — this is a plain HTTPS call to /v1/exchangerate with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/exchangerate",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/exchangerate
Install the C# / .NET SDK, then call the Exchange Rate API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.ExchangeRateusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/exchangerate");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/exchangerate
No SDK to install — this is a plain HTTPS call to /v1/exchangerate with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/exchangerate", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/exchangerate
No SDK to install — this is a plain HTTPS call to /v1/exchangerate with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/exchangerate");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/exchangerate
No SDK to install — this is a plain HTTPS call to /v1/exchangerate with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/exchangerate")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Exchange Rate form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Exchange Rate API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Exchange Rate API.
Finance
- Balance Sheet
- Benchmark Rate
- BIN Lookup
- Bitcoin Price
- Cash Flow Statement
- Company Lookup
- Cost of Living
- CPI Inflation
- Currency Converter
- Currency Symbols
- Dividends
- Earnings Report
- Ethereum Price
- Exchange Rate
- Financial Ratios
- GDP Data
- Global Stock Market
- Gold Price
- I-Bond Rates
- IFSC Lookup
- Income Statement
- Income Tax Brackets
- Income Tax Calculator
- Inflation Rate
- Insider Trading
- Interest Rate
- Jobs Report
- Loan Calculator
- Minimum Wage
- Mortgage Calculator
- Mortgage Rate
- National Debt
- Palladium Price
- Platinum Price
- Population Data
- Purchasing Power
- Routing Number Lookup
- Sales Tax Calculator
- Sales Tax Lookup
- Sanctions Screening
- SEC Filings
- Silver Price
- Stock Exchange
- Stock Market Open Times
- SWIFT Code Lookup
- Trade Balance
- Treasury Yields
- Unemployment Rate
- VAT Rates
Related articles
All articles →
Currency Conversion: Handling Exchange Rates CorrectlyExchange rates change constantly. Learn how to handle currency conversion in applications with accuracy and reliability.Read
Going Global: Building Multi-Currency AppsYour app works great in dollars. Now a customer in Germany wants to pay in euros. Here's what to know.Read
API Caching: The Cheapest Performance WinEvery duplicate API call is wasted money. Here's how to cache responses properly—and when not to.Read