FX Price History

The daily closing rate of one currency pair, ready to chart. It sits alongside FX Metric History, which carries the scores and metrics.

Request

curl https://api.bytetree.io/api/fx/EURUSD/prices

# With date range
curl "https://api.bytetree.io/api/fx/EURUSD/prices?from=2026-01-01&to=2026-01-31"

Path Parameters

Name	Type	Required	Description
`symbol`	`string`	Yes	Concatenated FX pair code (e.g. `EURUSD`). Case-insensitive

Query Parameters

Name	Type	Required	Description
`from`	`string`	No	Inclusive ISO `YYYY-MM-DD` start date
`to`	`string`	No	Inclusive ISO `YYYY-MM-DD` end date
`format`	`string`	No	Response format: `json` (default), `csv`, or `toon`

Response

Field	Type	Description
`symbol`	`string`	The normalised (uppercase) symbol
`count`	`number`	Number of data points returned
`data`	`array`	Array of daily price records, sorted ascending by date

Each record in data:

Field	Type	Description
`date`	`string`	ISO 8601 date
`close`	`number`	Daily close rate

{
  "symbol": "EURUSD",
  "count": 2,
  "data": [
    { "date": "2026-05-04T00:00:00.000Z", "close": 1.16720 },
    { "date": "2026-05-05T00:00:00.000Z", "close": 1.16838 }
  ]
}

Errors

Status	Description
`404`	The symbol has no FX records. Note: an unknown but otherwise well-formed symbol (e.g. `XYZUSD`) is treated the same as a known symbol with no data

Why close-only

FX rates are conventionally rendered as line series, not candlesticks — intraday OHLC isn’t meaningful for daily-fix FX, and ByteTree’s own FX charts are line-only. The endpoint reflects that convention rather than padding the row with synthetic open/high/low/volume fields.

For raw OHLC rate data (where open, high, low, close and dates do exist on the underlying record) see /api/rates/:pair.

Polymorphic equivalent

GET /api/prices/:symbol also resolves FX symbols and returns the same { date, close } shape for FX (no synthetic OHLC). Use this endpoint when the consumer is FX-only; use the polymorphic surface when iterating across mixed asset types.

Notes

Without from/to, returns all available history for the pair.
For computed FX metrics (ByteTrend scores, trend regimes, MA deviations) see /api/fx/:symbol/series.