Historical FX docs
Open the related NovaDataHub page for deeper documentation, comparisons, or implementation guidance.
Historical FX reporting becomes easier when the workflow is split into clear stages: period definition, time-series retrieval, normalization, and downstream reporting. This tutorial shows one practical way to structure that pipeline.
Start with the exact window the report needs, such as a billing month, reconciliation period, or finance reporting range.
Call the historical FX endpoint with a clear base currency, symbol set, and date range.
GET /api/fx/timeseries?base=EUR&symbols=USD,GBP&start=2024-01-01&end=2024-01-31Transform the returned JSON into date-based rows or report-friendly structures so analytics and finance consumers can query it easily.
Historical FX values are most useful once they are connected to invoices, product metrics, billing events, or reporting periods from your own systems.
When the report is generated, keep the period, base currency, and target symbols visible so the output remains auditable and easy to interpret.
Open the related NovaDataHub page for deeper documentation, comparisons, or implementation guidance.
Open the related NovaDataHub page for deeper documentation, comparisons, or implementation guidance.
Open the related NovaDataHub page for deeper documentation, comparisons, or implementation guidance.
Open the related NovaDataHub page for deeper documentation, comparisons, or implementation guidance.