Key points
- Designed for direct amount conversion workflows.
- Works well in pricing previews, billing estimates, quoting, and checkout support flows.
- Conversion responses are intentionally compact so they can be passed straight into product logic.
Updated on 2026-05-12
NovaDataHub Engineering
Developer docs
FX Conversion Endpoint
The FX conversion endpoint is the fastest path from one currency amount to another. It is a strong fit when product code needs a direct converted value instead of a full table of rates.
Common errors
- 400 from and to are required
- 400 rate not found
- 401 invalid_key
- 429 rate_limited
Reference details
Parameters, response shape, and operational notes
Parameter notes
- from and to are the required currency parameters.
- amount should be preserved with the returned rate so later calculations remain auditable.
- This endpoint is most useful when you need a direct answer rather than a broader rates table.
Response highlights
- Look for from, to, amount, rate, result, and date in the response.
- The rate is often worth storing alongside the result so downstream systems can explain how the conversion happened.
- This endpoint is different from latest-rates fetches because the output is already shaped for a single conversion task.
Operational notes
- Keep user-facing pricing logic and operator-facing reporting logic separate if they use the same FX input layer.
- Validate supported currencies before exposing the conversion flow to customers.
- Use current-rate and historical endpoints alongside conversion only when your workflow actually needs both.
Implementation checklist
- Start with a one-amount conversion request to confirm the response shape.
- Decide whether the result is transient UI data or something that must be stored for auditing or invoices.
- Add input validation around currency symbols and decimal handling before pushing the endpoint into production checkout flows.
Code examples
Visible integration examples
curl
curl -s -H "x-api-key: YOUR_API_KEY" "https://novadatahub.com/api/fx/convert?from=USD&to=INR&amount=100"Python
import requests
resp = requests.get('https://novadatahub.com/api/fx/convert', params={'from': 'USD', 'to': 'INR', 'amount': 100}, headers={'x-api-key': 'YOUR_API_KEY'}, timeout=60)
print(resp.json())C# HttpClient
using System.Net.Http.Json;
using System.Text.Json;
using var http = new HttpClient();
http.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await http.GetFromJsonAsync<JsonElement>("https://novadatahub.com/api/fx/convert?from=USD&to=INR&amount=100");
Console.WriteLine(json.ToString());Sample JSON response
{
"ok": true,
"from": "USD",
"to": "INR",
"amount": 100,
"rate": 83.21,
"result": 8321.0,
"date": "2026-05-11"
}Related resources
Move from reference docs into the next relevant workflow
Currency Exchange API landing page
Open the main FX overview page for current rates, conversion, and historical data use cases.
Open landing pageFX response fields
Map base, date, rates, conversion values, and time-series structures into cleaner downstream models.
Open docsAPI playground workflow
Validate rate, conversion, or historical requests before wiring pricing, checkout, or reporting logic.
Open docsMulti-currency checkout guide
Read the implementation guide for base-currency design, fallbacks, and pricing consistency across surfaces.
Open guideHistorical FX reporting tutorial
Follow a practical workflow for date-range retrieval, normalization, and reporting-ready storage.
Open tutorialFX comparison page
See what product and finance teams should evaluate when choosing an FX API for pricing and reporting.
Open comparisonRelated links