Currency Converter API
Overview
To use Currency Converter, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/currencyconverterExample
How to call the Currency Converter API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/currencyconverter?value=1&from=USD&to=EUR" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/currencyconverter?value=1&from=USD&to=EUR', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/currencyconverter?value=1&from=USD&to=EUR', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/currencyconverter?value=1&from=USD&to=EUR", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"from": "USD",
"to": "EUR",
"value": 1,
"convertedValue": 0.921456,
"rate": 0.921456,
"change24h": -0.002134,
"change24hPct": -0.2312,
"changeDirection": "down",
"high24h": 0.924521,
"low24h": 0.919823
}
}Authentication
The Currency Converter API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Currency Converter API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Currency Converter API:
Convert Currency Rates
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
value | number | required | The amount to convert Range: min: 0 | - | |
from | string | required | The ISO 4217 currency code to convert from | - | |
to | string | required | The ISO 4217 currency code to convert to | - |
Response
The Currency Converter API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<from>USD</from>
<to>EUR</to>
<value>1</value>
<convertedValue>0.921456</convertedValue>
<rate>0.921456</rate>
<change24h>-0.002134</change24h>
<change24hPct>-0.2312</change24hPct>
<changeDirection>down</changeDirection>
<high24h>0.924521</high24h>
<low24h>0.919823</low24h>
</data>
</response>
status: ok
error: null
data:
from: USD
to: EUR
value: 1
convertedValue: 0.921456
rate: 0.921456
change24h: -0.002134
change24hPct: -0.2312
changeDirection: down
high24h: 0.924521
low24h: 0.919823
| key | value |
|---|---|
| from | USD |
| to | EUR |
| value | 1 |
| convertedValue | 0.921456 |
| rate | 0.921456 |
| change24h | -0.002134 |
| change24hPct | -0.2312 |
| changeDirection | down |
| high24h | 0.924521 |
| low24h | 0.919823 |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
from | string | Source currency code (e.g., USD, EUR) | |
to | string | Target currency code (e.g., USD, EUR) | |
value | number | Original amount to convert | |
convertedValue | number | Converted amount in target currency | |
rate | number | Current exchange rate for the currency pair | |
change24hPremium | number | Rate change vs 24 hours ago | |
change24hPctPremium | number | Percentage rate change vs 24 hours ago | |
changeDirection | string | Direction of 24h change: up, down, or unchanged | |
high24hPremium | number | Highest rate in the past 24 hours | |
low24hPremium | number | Lowest rate in the past 24 hours |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Currency Converter through GraphQL to combine it with other API calls in a single request. Query only the currency converter data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
currencyconverter(
input: {
value: 1
from: "USD"
to: "EUR"
}
) {
from
to
value
convertedValue
rate
change24h
change24hPct
changeDirection
high24h
low24h
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Currency Converter API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Currency Converter requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Currency Converter API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Currency Converter
Official Currency Converter packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Currency Converter works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Currency Converter?
How many credits does Currency Converter cost?
Each successful Currency Converter API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful currency converter lookups.
Can I use Currency Converter in production?
The free plan is for testing and development only. For production use of Currency Converter, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Currency Converter from a browser?
What happens if I exceed my Currency Converter credit limit?
When you reach your monthly credit limit, Currency Converter API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








