ghostfolio

5851 Commits

29 Branches

790 Tags

335 MiB

Tree: 173ad7c631

Commit Graph

Author	SHA1	Message	Date
Robert Tidball	acf5f19b6e	Feature/add FXMacroData data provider for exchange rates Every multi-currency portfolio needs exchange rates, and the provider supplying them is configurable through DATA_SOURCE_EXCHANGE_RATES. This adds an option backed by official reference rates published by central banks and statistical authorities rather than scraped from a market data site. The provider handles currency pairs only, so any other symbol is left to the other providers. The covered currencies are discovered from the API rather than hardcoded: a pair is available whenever both of its currencies are covered, because the API stores each pair in one direction only and derives the inverse or the cross itself. That means the provider asks for the direction it wants instead of inverting a rate locally, and search can offer a cross the API derives but does not store. A rate is documented as anyOf[number, null], so a missing figure is skipped rather than recorded as a zero market price, and one unavailable pair does not lose the quotes of the others. Historical ranges are walked page by page because the endpoint caps a page at 100 rows. The API key is read from API_KEY_FXMACRODATA and sent as a header, so it is not written to request logs or a proxy's access log. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	1 month ago

Author

SHA1

Message

Date

Robert Tidball

acf5f19b6e

Feature/add FXMacroData data provider for exchange rates

Every multi-currency portfolio needs exchange rates, and the provider
supplying them is configurable through DATA_SOURCE_EXCHANGE_RATES. This adds
an option backed by official reference rates published by central banks and
statistical authorities rather than scraped from a market data site.

The provider handles currency pairs only, so any other symbol is left to the
other providers. The covered currencies are discovered from the API rather
than hardcoded: a pair is available whenever both of its currencies are
covered, because the API stores each pair in one direction only and derives
the inverse or the cross itself. That means the provider asks for the
direction it wants instead of inverting a rate locally, and search can offer
a cross the API derives but does not store.

A rate is documented as anyOf[number, null], so a missing figure is skipped
rather than recorded as a zero market price, and one unavailable pair does
not lose the quotes of the others. Historical ranges are walked page by page
because the endpoint caps a page at 100 rows.

The API key is read from API_KEY_FXMACRODATA and sent as a header, so it is
not written to request logs or a proxy's access log.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

1 month ago

1 Commits (173ad7c631ab1054ffe90a8d5f08e9a06f74e876)