0Pools API

0Pools is the approved-partner API for headless pool liquidity workflows. It lets an entitled partner discover the pools available to its account, request firm or indicative quotes, execute exactly once against a firm quote, poll or read trade state, and reconcile balance movements.

This reference is OpenAPI-backed and public-safe. It explains the contract partners can build against without exposing liquidity sources, routing internals, reserve allocation, treasury balances, provider names, market-maker terms, or runbooks.

Contract snapshot

The API is not self-serve. A valid key does not mean every pool, side, rail, balance gate, or environment is enabled. Your account entitlement decides which pools appear and which operations succeed.

What this API covers

• Entitled pool discovery and current partner-visible availability.
• Per-pool capabilities: sides, networks, limits, fees, spreads, tier, and balance gates.
• Firm quotes for executable short-lived locks.
• Indicative quotes for price-only previews.
• One-time idempotent execution against firm quotes.
• Status polling that can advance settlement.
• Pure trade reads for display, support, and reconciliation.
• Partner-visible balance and funding views.
• Partner-scoped ledger entries for balance reconciliation.

Public boundary

This reference covers partner-visible discovery, quote, transact, status, trade, funding, ledger, and balance behavior. It does not expose liquidity sources, provider names, route priority, market-maker terms, reserve levels, treasury account balances, top-up runbooks, or settlement worker internals.

Authentication map

Operation map

End-to-end lifecycle

The important split is between driver reads and display reads. GET /pools/transactions/{quoteId} can progress a reserved trade. GET /pools/trades and GET /pools/trades/{transactId} are pure reads for dashboards, support, and reconciliation.

Quote outcomes

Fail-soft 200 responses are intentional. Branch on available and executable, not just HTTP status.

Example: quote then execute

curl -X POST https://pools-api-sandbox.0bit.app/v1/pools/EUR-USDT/quote \
  -H "Authorization: Bearer sk_test_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "side": "on_ramp",
    "fiatCurrency": "EUR",
    "cryptoCurrency": "USDT",
    "amount": "100.00",
    "cryptoNetwork": "tron",
    "type": "firm",
    "destAddress": "0x52908400098527886E0F7030069857D2E4169EE7",
    "destNetwork": "arbitrum"
  }'

curl -X POST https://pools-api-sandbox.0bit.app/v1/pools/EUR-USDT/transact \
  -H "Authorization: Bearer sk_test_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 00000000-0000-4000-8000-000000000456" \
  -d '{ "quoteId": "pq_test_8f3c000000000123" }'

const quoteResponse = await fetch('https://pools-api-sandbox.0bit.app/v1/pools/EUR-USDT/quote', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.OBIT_POOLS_SECRET_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    side: 'on_ramp',
    fiatCurrency: 'EUR',
    cryptoCurrency: 'USDT',
    amount: '100.00',
    cryptoNetwork: 'tron',
    type: 'firm',
    destAddress: '0x52908400098527886E0F7030069857D2E4169EE7',
    destNetwork: 'arbitrum',
  }),
});

const quote = await quoteResponse.json();
if (!quote.available || !quote.executable) {
  throw new Error(`Pool unavailable: ${quote.unavailableReason ?? 'not executable'}`);
}

const tradeResponse = await fetch('https://pools-api-sandbox.0bit.app/v1/pools/EUR-USDT/transact', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.OBIT_POOLS_SECRET_KEY}`,
    'Content-Type': 'application/json',
    'Idempotency-Key': crypto.randomUUID(),
  },
  body: JSON.stringify({ quoteId: quote.quoteId }),
});

const trade = await tradeResponse.json();

import os
import uuid
import requests

quote = requests.post(
    "https://pools-api-sandbox.0bit.app/v1/pools/EUR-USDT/quote",
    headers={
        "Authorization": f"Bearer {os.environ['OBIT_POOLS_SECRET_KEY']}",
        "Content-Type": "application/json",
    },
    json={
        "side": "on_ramp",
        "fiatCurrency": "EUR",
        "cryptoCurrency": "USDT",
        "amount": "100.00",
        "cryptoNetwork": "tron",
        "type": "firm",
        "destAddress": "0x52908400098527886E0F7030069857D2E4169EE7",
        "destNetwork": "arbitrum",
    },
).json()

if not quote.get("available") or not quote.get("executable"):
    raise RuntimeError(f"Pool unavailable: {quote.get('unavailableReason')}")

trade = requests.post(
    "https://pools-api-sandbox.0bit.app/v1/pools/EUR-USDT/transact",
    headers={
        "Authorization": f"Bearer {os.environ['OBIT_POOLS_SECRET_KEY']}",
        "Content-Type": "application/json",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={"quoteId": quote["quoteId"]},
).json()

Object model

On-ramp and off-ramp behavior

For on-ramp delivery, the destination address is locked on the quote and copied to the trade. Do not collect a new destination address at transact time. For off-ramp, build only after your account has explicit enablement and the crypto-receipt path is confirmed.

Status model

The returned state is why a webhook-only integration is incomplete. Continue polling after settlement where your flow requires reversal detection, or reconcile the ledger on a schedule.

Reconciliation model

Store your own order id, pool id, quote id, trade id, idempotency key, request id, status, amount/rate strings, fee/spread bps, and timestamps. Those records let support investigate without any private route details.

Error and retry model

Production checklist

• Account has explicit 0Pools approval.
• Pool appears in GET /pools for the active environment.
• Your server reads capabilities before quoting.
• Browser code never uses sk_*.
• Amounts and rates are strings, never floats.
• Firm quote expiry is enforced in your UI.
• Transact uses a durable idempotency key.
• Status polling uses quoteId and recognizes terminal states.
• Trade reads are used for display and reconciliation.
• Ledger reconciliation runs after settlement and on a schedule.
• Support tooling can search by your order id, quote id, trade id, and request id.
• The UI never exposes source/provider/route internals.

Related pages