BaniPool Atlas

YOUR KEYS. YOUR CAPITAL.

EXPLORE

OverviewFind walletLiquidity poolsTokenNew pool radarWatchlist

YOUR CAPITAL

Wallet profileTransactionsAutomationSwap

ECOSYSTEM

Network statusDocumentationGuidesArticlesDevelopersSettings
BANIPOOL/Documentation

Search pools

Paste or type a pool address, pool ID, token address, or token symbol. All networks are searched at once.

A token address shows pools that use that token.

Create new pool

Connect wallet

Choose a wallet on this device or connect your phone wallet with a QR code.

Detected wallets

No browser wallet detected. Use WalletConnect for a wallet on your phone.

Signing in to view your portfolio does not authorize transactions.

Documentation

Errors & limits

The error response shape, the codes you may see, and how to handle them.

Error format

json
{
  "error": {
    "code": "INVALID_ACTION",
    "message": "Price impact di atas 5%; aktifkan Expert Mode, kurangi nominal, atau gunakan Manual.",
    "retryable": false,
    "details": {}
  },
  "requestId": "req_3c4e052c-0518-4079-946a-9b32894e3c25"
}

Include the requestId when reporting a problem. retryable: true means it is safe to retry after a pause.

Error codes

CodeHTTPMeaning
BAD_REQUEST400Invalid parameters; see details.issues.
UNAUTHENTICATED401Missing or expired key or session.
FORBIDDEN403Missing scope, not the owner, or CSRF protection.
NOT_FOUND404The resource does not exist.
CONFLICT409Version guard mismatch, quote already used, or state mismatch.
INVALID_ACTION422Action rejected by simulation/rules (slippage, price impact, balance, amount too small).
CAPABILITY_UNAVAILABLE422The feature is not available on this network or was stopped by the operator.
RATE_LIMITED429Rate limit/quota; wait for Retry-After.
DEPENDENCY_UNAVAILABLE503RPC or data provider problem; try again.
INTERNAL500Server error; report it with the requestId.

Recommended practices

  • Use the same Idempotency-Key when retrying the same mutation, so you never create duplicate quotes/keys.
  • Only retry retryable errors with exponential backoff; never auto-repeat on-chain transactions.
  • Check meta.partial and dataStatus before using data; networks with problems are reported, not filled with zeros.