Currency Converter API

About the Currency Converter API

Currency Converter works by analyzing the amount and currency provided and converting the currency rate. It uses advanced algorithms to convert the currency rate based on the amount and currency and returns the converted currency rate.

What people use it for

Multi-Currency Storefront Checkout

E-commerce platforms convert catalog prices to shoppers' local currencies and display current exchange rates at checkout before processing payment.

Cross-Border Expense Reporting

When employees submit foreign travel receipts, accounting software converts reimbursable expenses into company base currency using the exact exchange rate.

International Invoice Generation

Generate export invoices in foreign buyer currencies by calculating converted subtotals and showing whether the exchange rate moved up or down.

Travel Card Expense Tracking

To prevent surprise foreign transaction charges, mobile banking apps calculate local currency balances on the fly using real-time conversion rates.

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

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — GET /v1/currencyconverter

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

1
2

curl "https://api.apiverve.com/v1/currencyconverter?value=1&from=USD&to=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.

Response — GET /v1/currencyconverter

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.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

{
  "status": "ok",
  "error": null,
  "data": {
    "from": "USD",
    "to": "EUR",
    "value": 1,
    "convertedValue": 0.866496,
    "rate": 0.866496,
    "change24h": 0.000493,
    "change24hPct": 0.0569,
    "changeDirection": "up",
    "high24h": 0.866914,
    "low24h": 0.865725,
    "lastUpdated": "2026-09-15T21:00:17.674Z"
  }
}

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.

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.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

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.

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.

Zero-code embed — one snippet, no backend

Drop an interactive Currency Converter 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 — Currency Converter 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.

Currently v1Data refreshed realtime