Skip to content
Request a demoGet in touch
Get in touch
← Back to documentation

Partner API & Monitoring Integrations

For an exchanger, listings on monitoring services (BestChange and similar) are the primary client source. The platform generates a BestChange-compatible rate export automatically: the feed is built from current on-demand rates including your markup and reserves. This page explains how it works and what monitoring services require.

Rate export for monitoring services

In the admin panel, the integrations section provides the feed URL:

https://your-domain.com/export/bestchange.xml
The feed is generated on every request from current platform data (on-demand): the monitoring service always fetches fresh rates, no separate synchronization needed.

Simplified feed example:

<?xml version=”1.0″ encoding=”UTF-8″?>
<rates>
<item>
<from>BTC</from>
<to>USDTTRC20</to>
<in>1</in>
<out>98507.39</out>
<amount>150000</amount>
<minamount>0.002 BTC</minamount>
<maxamount>2 BTC</maxamount>
</item>
<item>
<from>USDTTRC20</from>
<to>BTC</to>
<in>1000</in>
<out>0.00992</out>
<amount>3.2</amount>
<minamount>200 USDT</minamount>
<maxamount>50000 USDT</maxamount>
</item>
</rates>

  • <in> / <out> — the exchange ratio at the final rate (including your markup).
  • <amount> — the direction reserve (see Reserves).
  • Only active directions with a non-zero reserve and working merchants make it into the feed.

Monitoring service requirements

Typical listing checklist (BestChange example):

  • Feed available 24/7 — the URL must respond without authorization and with minimal response time. The platform ensures this on its side.
  • Rate freshness — the rate in the feed must match the rate on the site at the moment of checking. The on-demand model covers this requirement out of the box: the site and the feed compute one and the same formula.
  • Honest reserves — <amount> must reflect the real ability to pay out. Inflating reserves is a reason for delisting on complaint.
  • Working site over HTTPS — domain, SSL, no redirects to other brands.
  • Exchange rules — a public page with regulations (payout times, refund terms, KYC/AML policy).
  • Domain age and reputation — monitoring services may request a deposit or additional checks for new brands.

Working with monitoring services in practice

  • Rate and position. Listing position is determined by the rate: the lower your total markup on a pair, the higher the row. Manage markup per direction deliberately (see Rate Formation).
  • Watch the reserves. A direction with an empty reserve drops out of the feed — to the monitoring service this looks like the direction was taken down. Set up low reserve notifications.
  • Rate verification. Monitoring services periodically reconcile the feed against the site with test orders. A mismatch between feed and widget rates is a typical cause of warnings; on the platform the rate source is unified — don’t break it with manual overrides outside the markup.
  • Quote lifetime. If a monitoring service asks for a guaranteed rate TTL, use rate fixing at order creation (see API v1).

Custom integrations

The same export is available in machine-readable JSON for your own systems (aggregators, rate comparison Telegram bots):

GET https://your-domain.com/export/rates.json

The format mirrors the XML feed: the same directions, rates, and reserves, updated on demand.

See also