FX Response Fields

FX integrations become easier to trust when teams are clear about which fields belong to latest-rate lookups, which belong to direct conversions, and which belong to historical reporting. This page explains how to think about the main NovaDataHub FX response shapes so pricing, checkout, and finance workflows model the data cleanly.

curl -s -H "x-api-key: YOUR_API_KEY" "https://novadatahub.com/api/fx/rates?base=USD&symbols=EUR,GBP"

import requests
rates = requests.get('https://novadatahub.com/api/fx/rates', params={'base': 'USD', 'symbols': 'EUR,GBP'}, headers={'x-api-key': 'YOUR_API_KEY'}, timeout=60).json()
print(rates.keys())

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/rates?base=USD&symbols=EUR,GBP");
Console.WriteLine(json.ToString());

{
  "latest": {
    "ok": true,
    "base": "USD",
    "date": "2026-05-11",
    "rates": { "EUR": 0.92, "GBP": 0.78 }
  },
  "convert": {
    "ok": true,
    "from": "USD",
    "to": "EUR",
    "amount": 100,
    "rate": 0.92,
    "result": 92.0,
    "date": "2026-05-11"
  }
}