Anonymous Cryptocurrency Exchange
No hidden fees → No delays → No registration
no KYC | no logs | no analytics | TOR
Navigation
Anonymous Cryptocurrency Exchange
No hidden fees → No delays → No registration
no KYC | no logs | no analytics | TOR
API information
General information
DEX.fo publishes all live exchange directions, rates, reserves and limits as a single XML document.
The feed accepts GET requests, requires no API key and no registration.
Encoding is UTF-8, content type application/xml; charset=utf-8.
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.
Request parameters
None
Response parameters
The root element is <rates>. It contains one <item> 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 — Amount of from that corresponds to out
out — Amount of to given for in units of from, service fee included
amount — Reserve of the to currency (the amount we are capable of sending)
minamount — Optional minimum deposit, in the from currency; omitted when there is no lower bound
maxamount — Optional maximum deposit, in the from 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
A direction is written as “in of from → out of to”. 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.
The service fee is already included in in / out — nothing extra has to be subtracted by the client. Network fees of the outgoing transaction are covered by DEX.fo.
When present, minamount and maxamount are inclusive bounds expressed in the from 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
The from and to 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 |
Bitcoin
Bitcoin
Ethereum
Ethereum
Litecoin
Litecoin
Monero
Monero
Tether USD (ERC-20)
Ethereum
Tether USD (TRC-20)
Tron
USD Coin (ERC-20)
Ethereum
Codes are case-sensitive. For multi-network assets the network is part of the code, so USDTERC20 and USDTTRC20 are never interchangeable.
Additional notes
Directions are independent: BTC → LTC and LTC → BTC 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.
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 503 Service Unavailable and a JSON error; it does not return an empty <rates> document.
Rates are informational and are locked at the moment an exchange order is created.
Questions about integration — see Contacts.