01
Private updates
Start with recurring paid refreshes of the audited Parquet bundle and release manifest.
API and Update SubscriptionForex data updates
Forex data updates
without rebuilding ingestion
HistoricalFX is starting with audited file bundles. The recurring product path is an update subscription and API layer for teams that need refreshed datasets, manifests, and validation reports.
What we are validating
Refresh cadenceMonthly first
Primary formatParquet
Proof layerRelease manifests
Buyer fitTeams and developers
API use cases
Recurring monthly data refreshes without rebuilding your own ingestion pipeline.
Release manifests that expose row counts, timestamps, and known limitations.
Signed file delivery for Python, DuckDB, research notebooks, and internal tools.
Commercial validation reports for teams that need defensible market-data inputs.
Build path
02
Manifest API
Expose pair coverage, row counts, timestamps, and quality flags through a lightweight endpoint.
03
Data delivery API
Offer scoped signed downloads and customer-specific update feeds after licensing is proven.
API and update questions
Is the HistoricalFX API live today?+
Not as a public self-serve API. The first recurring offer is private audited refresh delivery with manifests, then a manifest API once paid demand is proven.
What would an update subscription include?+
The starting offer is refreshed Parquet files, release manifests, coverage summaries, and validation notes for agreed symbols and cadence.
Can I request daily forex updates?+
Yes, but daily cadence is scoped case by case. Monthly or weekly refreshes are the first practical delivery path while the source-backed pipeline is hardened.
Will this replace a broker or live trading feed?+
No. HistoricalFX is focused on historical and refreshed research datasets, not live execution, account data, or broker order routing.
What formats are planned?+
Parquet is the primary delivery format. CSV, DuckDB, signed file feeds, or lightweight JSON manifest endpoints can be scoped after the workflow is clear.
Need recurring FX data?
Tell us your pairs, refresh cadence, format, and licensing constraints. API demand will shape the first subscription product.
Which symbols must be updated?
How often do you need refreshes?
What format fits your workflow?
What budget makes this worth buying?