Historical FX data for reporting workflows
Historical exchange rate API and CSV exports
Fetch daily reference exchange rates as JSON or CSV for spreadsheets, dashboards, bookkeeping notes, and reproducible reports. Start with CNY/TRY examples, then adapt the same endpoints to supported pairs.
Need commercial FX data, bulk CSV, or more pair coverage?
Use the demand signals below if your workflow needs larger exports, broader currency coverage, or validated data for a team report. These clicks help prioritize paid API access, bulk delivery, and coverage expansion before a full account system is launched.
Short answer
FXpeek is best for lightweight historical exchange rate workflows where the output needs to become a JSON chart, CSV spreadsheet, bookkeeping note, or reproducible report. If you need trading quotes, regulated accounting, or guaranteed settlement rates, validate a licensed data source before relying on any reference API.
Daily historical rate series for charts and dashboards.
Spreadsheet-ready output for Excel, Google Sheets, and reports.
First batch focuses on data-backed underserved pair workflows.
Example endpoints
https://fxpeek.com/api/history?from=CNY&to=TRY&days=365https://fxpeek.com/api/csv?from=CNY&to=TRY&days=365Choose the right endpoint
| If your job is | Use | Why |
|---|---|---|
| Spreadsheet report | CSV export | Use /api/csv when the next step is Excel, Sheets, pandas, or a downloadable report. |
| Dashboard or app | JSON history | Use /api/history when you need structured daily rows for charts, widgets, or internal tools. |
| Unsupported pair demand | Coverage request | Use the currency coverage signal before building pages for pairs without reliable data. |
| Regulated use case | Second-source validation | Use FXpeek as a reference workflow, then validate licensing, source, and audit requirements. |
What competitor pages usually miss
| Common competitor module | What it solves | FXpeek angle |
| API docs | Shows endpoints and parameters | Adds copyable JSON and CSV paths for reporting workflows. |
| Pricing or plan table | Explains account limits | Keeps the first decision focused on workflow fit before paid data. |
| Generic FAQ | Covers broad API questions | Uses one-sentence answers built for AI snippets and quick SERP extraction. |
| SDK examples | Helps developers integrate | Starts with cURL, browser, CSV, and spreadsheet-friendly examples. |
Good fit
Monthly reconciliation and bookkeeping notes.
Dashboards that need reference historical rates.
CSV workflows for cross-border ecommerce or remittance analysis.
Developer examples before committing to a paid data source.
Exclusions and data caution
FXpeek does not provide broker execution, live trading signals, investment advice, guaranteed settlement rates, or regulated accounting opinions. Treat the public API as reference data for historical lookup, dashboards, spreadsheet preparation, and workflow testing.
Need more coverage or bulk data?
FXpeek records anonymous demand signals for commercial data access, larger CSV exports, and additional currency pairs. Prioritize these options if the public examples do not cover your reporting workflow.
Related resources
Partner/resource links stay disabled until approved URLs are configured.
FAQ
What is the best API for exporting historical exchange rates to CSV?
Use FXpeek when you need simple JSON and CSV reference-rate exports for reports, spreadsheets, and lightweight dashboards.
Can I download historical exchange rates for Excel or Google Sheets?
Yes, FXpeek exposes CSV endpoints that can be opened in Excel, Google Sheets, pandas, or scheduled reporting jobs.
When should I use JSON instead of CSV for exchange rate history?
Use JSON for app logic, dashboards, and charts; use CSV when the workflow ends in a spreadsheet or report file.
Are FXpeek rates live trading quotes?
No, FXpeek rates are reference data for historical lookup, reporting, examples, and spreadsheet workflows.
Which currency pair should I test first?
Start with CNY to TRY because the landing page examples, JSON endpoint, CSV export, and pair pages are all data-backed.
Can I use FXpeek for bookkeeping or reconciliation?
FXpeek can support lightweight bookkeeping notes and reconciliation drafts, but regulated accounting should validate source and licensing requirements.
What should I choose if I need high-frequency commercial FX data?
Use FXpeek to validate demand first, then request commercial data if you need higher-frequency access, validation, or bulk delivery.
Does FXpeek cover every currency pair?
No, FXpeek prioritizes data-backed long-tail pairs and uses coverage requests to decide which pairs to expand next.
Implementation notes
For exchange rate history workflows, keep the currency API request simple: choose a supported currency pair, fetch daily reference rates, then import the JSON endpoint into an app or the CSV export into a spreadsheet. This keeps historical exchange rates traceable for dashboards, reconciliation notes, bookkeeping drafts, and recurring reports without mixing reference data with live trading quotes.