XRBitcoinCashXRP Ledger trading & tools
TOOLS
API v1 · Developer preview

Build with
XRBitcoinCash.

Bring XRPL market data, trade previews and project intelligence into your own site or application.

Try a request Download OpenAPI
GET /api/v1/projectJSON
{
  "data": {
    "name": "XRBitcoinCash",
    "symbol": "XRBC",
    "circulatingSupply": null
  },
  "meta": {
    "network": "XRPL Mainnet",
    "apiVersion": "1.0.0"
  }
}
Abbreviated response shape. Unknown data stays null.
12 toolsOne developer catalog
22 API routesVersioned JSON contracts
Source-labeledLedger checkpoint and evidence limits
Wallet approvedProtected analytics access

A shared foundation

Your interface. XRBC data underneath.

Public endpoints need no API key. Protected services verify a signed Xaman session and the same XRBC holding thresholds used by the tools.

Markets & liquidity

Inspect exact token identity, XRP reserves, issuer obligations and bounded funded order books.

Test market data →

Trade previews

Compare modeled AMM and order-book outputs, price impact and partial fills before opening a wallet trading flow.

Explore quote endpoints →

Tool evidence

Use issuer restrictions, holder exposure, pool history, concentration and current monitoring thresholds.

See tool coverage →

Settlement & tokenization

Match validated payments to invoices and assess the completeness of submitted tokenization evidence.

View data contracts →
Check the live service. The playground reads the deployed API. Use the protected-access check below to see whether wallet authentication is configured. Public endpoints need no API key.

Make your first request.

Service not checked yet

Choose a public endpoint. Requests go directly to the XRBC backend and never ask for wallet credentials.

Exact XRBC currency and issuer, project links and explicit unknown supply fields.
ResponseNo request sent
Choose an endpoint and send a request to see its response.


API reference
Small endpoints. Clear contracts.
All paths below are relative to . Download the OpenAPI file for request schemas, response conventions and error codes.


Coverage & access
Built around the tools you already use.
Holding thresholds apply to the signed wallet at the time of each protected request. A token symbol alone never identifies the qualifying asset.
ToolMinimum XRBCWhat v1 provides
Know the scope. Extended Auditor, Risk Lens and Sentinel Forensics return evidence with their full composite scores withheld. Advanced Tokenization reports missing external data. Watchtower returns a current snapshot; continuous monitoring and stored history are not hosted by this release.


Protected access
A signed wallet. A short-lived session.
Protected access has not been checked.
Check service readiness before starting a wallet sign-in. This check does not request a signature.
  1. Create a challenge. Send the wallet’s classic address and requested tool IDs to POST /auth/challenges. Keep the returned challenge secret private.
  2. Approve in Xaman. Open the returned sign-in URL. The user approves a mainnet SignIn; it does not send a payment.
  3. Verify the result. After approval, send the challenge ID and private secret to POST /auth/sessions. The backend verifies the response directly with Xaman.
  4. Call a protected endpoint. Use the returned bearer token for up to five minutes. The server rechecks current XRBC holdings before each report or Value Path quote.
Authorization: Bearer YOUR_SESSION_TOKEN
Content-Type: application/json
Sessions are per user. Keep tokens in memory, discard them on logout and call DELETE /auth/session. Never put a wallet seed, private key, Xaman application secret or Live Coin Watch key in your frontend.
Protected endpoints require Xaman application credentials configured privately on the backend. An API response of authentication_unconfigured means that setup is still pending.


Integration notes
Keep the evidence with the result.
  • Amounts: ledger amounts are decimal strings. Modeled outputs, ratios and concentration are approximate; do not convert exact invoice amounts to JavaScript numbers for comparison.
  • Freshness: use the returned ledger hash, index, close time and age. The API rejects stale ledger checkpoints. A quote estimate lasts 15 seconds and can change before signing.
  • Execution: this API does not sign or submit transactions. Build your integration around explicit wallet review and an executable quote from the trading flow.
  • Rate limits: 60 requests per IP per minute; 12 protected requests per session per minute; one protected request at a time. Honor Retry-After on 429/503 responses.
  • Receipt reuse: record accepted transaction hashes and invoice IDs in your own durable database before crediting an invoice.
  • Market coverage: AMM reserve ratios are not last-trade prices. This release does not publish a 24-hour trade volume, verified circulating supply or market cap.
  • Attribution: retain XRBitcoinCash attribution, source, timestamp and limitations when displaying results. Third-party reference feeds have their own terms.
For a larger integration or additional endpoint, contact XRBitcoinCash.


Cross-check independently
Follow the source.
Project identity is the currency and issuer together. Market references and tool outputs do not establish a listing, endorsement or independently audited project status.
Currency  5852626974636F696E6361736800000000000000
Issuer    rEjwniYhYR5QDZzK1a1x2359j8j8N43Ypw
Network   XRP Ledger Mainnet
Issuer on Bithomp ↗ · XRPL API documentation ↗ · Xaman documentation ↗