XE APIxe.com ↗
Access live mid-market rates, currency conversion, historical time-series, and currency metadata from xe.com across 7 endpoints.
What is the XE API?
The XE.com API exposes 7 endpoints covering live mid-market exchange rates, currency conversion, historical chart data, and currency metadata sourced from xe.com. The get_all_rates endpoint returns rates for every supported currency relative to USD in a single call, while get_live_exchange_rate computes cross-rates for any arbitrary pair on demand. Coverage includes fiat currencies, cryptocurrencies, and obsolete currencies flagged through the get_currency_symbols endpoint.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/09357179-44fd-4bda-a0b3-32f011cff868/get_all_rates' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace xe-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""
XE Currency Exchange API - Usage Example
Get your API key from: https://parse.bot/settings
"""
from parse_apis.xe_currency_exchange_api import Xe, Currency, CurrencyPairing
xe = Xe()
# Get the full rate sheet (all currencies vs USD)
rate_sheet = xe.ratesheets.get()
print(rate_sheet.timestamp, rate_sheet.rates["EUR"])
# Convert 500 EUR to JPY
result = xe.exchangerates.convert(from_currency="EUR", to_currency="JPY", amount=500)
print(result.from_currency, result.to_currency, result.mid_market_rate, result.converted_amount)
# Get historical chart data for USD/GBP
chart = xe.chartdatas.get(from_currency="USD", to_currency="GBP")
for batch in chart.batch_list:
print(batch.start_time, batch.interval, len(batch.rates))
# List all supported currencies
for currency in xe.currencies.list():
print(currency.code, currency.is_obsolete, currency.is_sellable)
# Get country for a specific currency and its popular pairings
usd = xe.currency("USD")
country_info = usd.get_country()
print(country_info.country)
for pairing in usd.popular_pairings():
print(pairing.from_currency, pairing.to_currency, pairing.rate, pairing.trend)
Get all mid-market exchange rates relative to USD. Returns a timestamp and a rates object mapping every supported currency code to its USD-relative rate. The rate sheet refreshes every few minutes.
No input parameters required.
{
"type": "object",
"fields": {
"rates": "object mapping currency codes (e.g. EUR, GBP, JPY) to their exchange rate relative to 1 USD",
"timestamp": "integer, Unix timestamp in milliseconds of the rate snapshot"
},
"sample": {
"data": {
"rates": {
"EUR": 0.8670284684,
"GBP": 0.7484871598,
"JPY": 160.5393674776,
"USD": 1
},
"timestamp": 1781134560000
},
"status": "success"
}
}About the XE API
Live Rates and Currency Conversion
The get_live_exchange_rate endpoint accepts from, to, and an optional amount parameter, returning mid_market_rate, converted_amount, and a millisecond-precision timestamp. The convert_currency endpoint is functionally similar but requires amount, making it the straightforward choice when you always have a conversion quantity. Both return the same six-field response shape. For bulk needs, get_all_rates returns the full rates object mapping every currency code to its USD-relative value alongside a single timestamp.
Historical and Trend Data
get_historical_chart_data takes from and to currency codes and returns a batchList array where each batch contains a startTime, an interval in milliseconds (daily, hourly, or 15-minute granularity), and a rates array of numbers. This lets you reconstruct a multi-resolution time series for a given pair. The get_popular_currency_pairings endpoint accepts an optional base currency and returns current rate, trend direction (up, down, or null), rateChange, and percentageChange for commonly tracked pairs — useful for building dashboards that surface movement at a glance.
Currency Metadata
get_currency_symbols returns an object keyed by currency code. Each entry includes boolean flags: isObsolete, isSellable, isBuyable, and isCrypto (present when applicable). This is the right endpoint for filtering out defunct currencies or separating crypto from fiat before populating a UI selector. get_currency_details maps a single currency code to its ISO 2-letter country code — a small but useful lookup when you need to associate a currency with a specific country for display or routing logic.
The XE API is a managed, monitored endpoint for xe.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when xe.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official xe.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Display live EUR/USD and GBP/JPY rates on a fintech dashboard using
get_live_exchange_rate - Populate a multi-currency checkout with converted totals via
convert_currencywith a specifiedamount - Build a currency trend widget showing rate movement direction and percentage change from
get_popular_currency_pairings - Chart historical exchange rate fluctuations at daily, hourly, and 15-minute resolution using
get_historical_chart_data - Filter a currency selector to exclude obsolete and non-buyable currencies using
isSellableandisObsoleteflags fromget_currency_symbols - Map currency codes to country flags or locales using the
countryfield fromget_currency_details - Sync a full rates snapshot for all currencies in one request with
get_all_ratesfor offline or cached processing
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does XE.com have an official developer API?+
What granularities does `get_historical_chart_data` return?+
batchList array where each batch carries a startTime, an interval value in milliseconds, and a rates array. The intervals cover daily, hourly, and 15-minute periods, so you get three overlapping time-series batches in a single response. There are no query parameters to select a specific granularity — all three are returned together.Does `get_popular_currency_pairings` let me specify which pairs to retrieve?+
base currency code can be passed as input; you cannot specify an explicit list of target currencies. The endpoint returns whichever pairings XE.com surfaces as popular for that base. You can fork this API on Parse and revise it to filter or extend the returned pairs to match a custom list.Are bid/ask spread prices or bank transfer rates available?+
get_all_rates, get_live_exchange_rate, and convert_currency — return mid-market rates only. Bid, ask, and retail transfer rates are not exposed. You can fork this API on Parse and revise it to add an endpoint targeting spread or transfer rate data if that surface becomes available.What does the `isCrypto` flag in `get_currency_symbols` cover?+
isCrypto boolean is present on entries that represent cryptocurrency codes rather than fiat currencies. It is only included in the response object when it applies, so its absence on a given currency code indicates fiat. The endpoint does not return additional metadata such as blockchain network, contract address, or trading volume — those fields are not part of the response. You can fork this API on Parse and revise it to add a crypto-specific detail endpoint if needed.