Exchange | Dex.fo

General information

DEX.fo publishes all live exchange directions, rates, reserves and limits as a single XML document.

GET The feed accepts requests, requires no API key and no registration.

UTF-8 application/xml; charset=utf-8 Encoding is , content type .

https://dex.fo/api/v1/rates.xml

The document is regenerated every minute. Please do not poll more often than once every 60 seconds.

Requests that exceed the general API rate limit may be rejected. This protection is independent of the recommended polling interval.

GET /api/v1/rates.xml — Get exchange rates

Request parameters

None

Response parameters

<rates> <item> The root element is . It contains one per published exchange direction. The first five elements below are required; the limit elements are optional:

from — Currency the client sends

to — Currency the client receives

in from out — Amount of that corresponds to

out to in from — Amount of given for units of , service fee included

amount to — Reserve of the currency (the amount we are capable of sending)

minamount from — Optional minimum deposit, in the currency; omitted when there is no lower bound

maxamount from — Optional maximum deposit, in the currency

All numeric values are plain decimals with a dot separator, no thousands separators and no currency symbols. An item is published only while its reserve is positive. During a transient calculation failure, the previously published item may remain in the feed until it expires.

Reading a rate

in from out to A direction is written as “ of → of ”. The following formula estimates the received amount at the published effective rate:

estimated_received = sent / in * out

# 0.5 BTC → LTC
# 0.5 / 0.01279364 * 20.15456507 ≈ 787.67907 LTC

in out / are calculated for a probe amount, normally equivalent to USD 1,000 and clamped to the direction limits. Fixed network fees and price impact may vary with the deposit amount, so use the order calculator for an exact quote.

in out The service fee is already included in / — nothing extra has to be subtracted by the client. Network fees of the outgoing transaction are covered by DEX.fo.

minamount maxamount from When present, and are inclusive bounds expressed in the currency.

Example response

<?xml version="1.0" encoding="UTF-8"?>
<rates>
  <item>
    <from>BTC</from>
    <to>LTC</to>
    <in>0.01279364</in>
    <out>20.15456507</out>
    <amount>8628.9</amount>
    <minamount>0.00038381</minamount>
    <maxamount>6.39682308</maxamount>
  </item>
  <item>
    <from>USDTTRC20</from>
    <to>XMR</to>
    <in>1000.120004</in>
    <out>1.849276634393</out>
    <amount>1540.9</amount>
    <minamount>30.003601</minamount>
    <maxamount>150018.000659</maxamount>
  </item>
</rates>

Currency codes

from to The and elements use the following codes:

Code	Currency	Network
BTC	Bitcoin	Bitcoin
ETH	Ethereum	Ethereum
LTC	Litecoin	Litecoin
XMR	Monero	Monero
USDTERC20	Tether USD (ERC-20)	Ethereum
USDTTRC20	Tether USD (TRC-20)	Tron
USDCERC20	USD Coin (ERC-20)	Ethereum

BTC

Bitcoin

ETH

Ethereum

LTC

Litecoin

XMR

Monero

USDTERC20

Tether USD (ERC-20)

Ethereum

USDTTRC20

Tether USD (TRC-20)

Tron

USDCERC20

USD Coin (ERC-20)

Ethereum

USDTERC20 USDTTRC20 Codes are case-sensitive. For multi-network assets the network is part of the code, so and are never interchangeable.

Additional notes

BTC → LTC LTC → BTC Directions are independent: and are two separate items with their own rates and limits. A pair that is not present in the document is not offered at the moment of the request.

503 Service Unavailable <rates> If a technical problem prevents a new document from being built, the latest publishable snapshot continues to be served. If no snapshot is available or it becomes stale, the endpoint responds with and a JSON error; it does not return an empty document.

Rates are informational and are locked at the moment an exchange order is created.