Get FX Pair

Returns the latest computed metrics for a single FX pair. The canonical zero-ambiguity surface for single-pair lookups — see the FX Namespace overview for the polymorphic alternatives on /api/assets/:id and /api/metrics/:symbol/latest.

Request

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

# Lower case is fine — symbols are normalised
curl https://api.bytetree.io/api/fx/gbpjpy

Path Parameters

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

Response

Field	Type	Description
`data`	`object`	The synthesised FX record with metrics merged at the top level

The data object:

Field	Type	Description
`symbol`	`string`	The normalised (uppercase) symbol
`name`	`string`	Pretty slash form (e.g. `EUR/USD`)
`type`	`string`	Always `"fx"`
`date`	`string`	ISO 8601 date of the latest record
`close`	`number`	Latest close rate
metric fields	various	Computed metric fields merged at the top level — see Latest Metrics for the full set and definitions

{
  "data": {
    "symbol": "EURUSD",
    "name": "EUR/USD",
    "type": "fx",
    "date": "2026-05-05T00:00:00.000Z",
    "close": 1.16838,
    "byteTrendCapr200w": 4,
    "trendRegimeCapr200w": "Emerging Trend",
    "changeCapr200w": 1
  }
}

Errors

Status	Description
`404`	No rate data exists for the given symbol

Notes

Reserved sub-paths (/api/fx/:symbol/series, /api/fx/:symbol/prices where present) match before the bare /api/fx/:symbol route, so an FX pair that happens to collide with a sub-path word would not resolve here. The registered FX-pair set is finite and well-known, so this isn’t a practical concern.
For the polymorphic call that resolves stocks, crypto, FX, and other types through a single path, see /api/assets/:id.