Rabby Wallet API integration services (EVM OpenData & DeFi portfolio sync)

1. Portfolio aggregation API

Pulls total USD value, per-chain token balances, staked assets, and LP positions for any EVM address the user has connected in Rabby. Powers treasury dashboards, fund-of-funds reporting, and client-facing net-worth screens. Under the hood we use getTotalBalance, getTokenList, and per-chain protocol calls, then normalize symbols, decimals, and price oracles.

2. Transaction history & statement module

Exports swap, bridge, transfer, and contract-call history with timestamps, gas in wei and fiat, counterparty addresses, protocol names (Uniswap, Aave, 1inch, etc.), and categorized tags. Supports date range, chain filter, and pagination. Use case: generating tax-ready statements or feeding a general-ledger system.

3. DeFi position & yield module

Fetches open lending, borrowing, staking, and LP positions per protocol, including claimable rewards, health factors, and liquidation thresholds. Specific use: a risk desk that needs per-wallet borrow exposure on Aave / Spark / Venus refreshed every 60 seconds.

4. Approval & allowance auditor

Enumerates outstanding ERC-20 and ERC-721 approvals (including unlimited-allowance flags) per connected wallet, plus Rabby's DApp connection list. Specific use: compliance alerts when a user has granted unlimited allowance to an unknown contract.

5. Signature-intent & simulation relay

Captures the result of Rabby's pre-transaction simulation (expected balance change, risk labels, target contract) and forwards it to your backend for logging, co-signing, or policy enforcement. Specific use: corporate wallets that require a second approver before any call with a negative simulated balance change.

6. Webhook & event stream

Push deltas (new transaction confirmed, new token detected, position liquidated, approval revoked) to your HTTPS webhook in near real time. Specific use: customer-facing notification services or automated rebalancing bots that must not rely on polling.

Sample 1 — Portfolio balance via rabby-api

// Node.js, using @rabby-wallet/rabby-api
import { OpenApiService } from '@rabby-wallet/rabby-api';

const rabby = new OpenApiService({
  store: { host: 'https://api.rabby.io' }
});
await rabby.init();

const address = '0xAbC...1234';
const total   = await rabby.getTotalBalance(address);
const tokens  = await rabby.getTokenList(address, 'eth');

// Response (trimmed):
// {
//   "total_usd_value": 18432.55,
//   "chain_list": [
//     { "id":"eth", "usd_value": 12330.10 },
//     { "id":"arb", "usd_value":  4102.20 }
//   ]
// }

Sample 2 — Transaction history export

POST /api/v1/rabby/history
Content-Type: application/json
Authorization: Bearer <ACCESS_TOKEN>

{
  "address":   "0xAbC...1234",
  "chains":    ["eth","arb","base","op","bnb"],
  "from_date": "2025-01-01",
  "to_date":   "2025-06-30",
  "types":     ["transfer","swap","bridge","approve"]
}

// 200 OK
{
  "cursor": "eyJ0IjoxNz...",
  "items": [
    {
      "tx_hash": "0x…",
      "chain":   "eth",
      "block":   19842011,
      "ts":      "2025-02-14T08:21:03Z",
      "type":    "swap",
      "protocol":"uniswap_v3",
      "in":  { "symbol":"USDC", "amount":"2000" },
      "out": { "symbol":"ETH",  "amount":"0.62"  },
      "gas_usd": 1.42,
      "risk_label": null
    }
  ]
}

Sample 3 — Simulation webhook

// Webhook pushed to your backend before user signs
POST https://your-backend.example.com/rabby/pre-sign
X-Signature: t=1735689600,v1=5b0c…

{
  "event":    "pre_sign_simulation",
  "wallet":   "0xAbC...1234",
  "chain_id": 1,
  "method":   "approve",
  "target":   "0x00000000219ab540356cBB839Cbe05303d7705Fa",
  "simulation": {
    "expected_balance_changes": [],
    "allowance_changes": [
      { "token":"USDT","spender":"0xUnknown","amount":"unlimited" }
    ],
    "risk_label": "unlimited_allowance_to_unverified"
  },
  "policy_hint": "require_second_approver"
}

// 200 -> allow; 403 -> block & prompt second signer

Deliverables checklist

• OpenAPI / Swagger specification covering every exposed endpoint
• Protocol & authorization flow report (EIP-1193, EIP-6963, rabby-api, DeBank OpenAPI)
• Runnable source in Python / Node.js / Go for portfolio, history, and webhook flows
• Postman collection, automated integration tests, and load-test notes
• Compliance guidance (MiCA, GDPR, FATF Travel Rule, sanctions screening)
• Operational runbook: rate limiting, retries, chain-outage handling

Engagement models

Source code delivery from $300: we hand over the runnable API source code and full documentation; you pay after delivery upon satisfaction.

Pay-per-call API billing: access our hosted endpoints directly and pay only for the calls you make — no upfront fee, ideal for teams that want to validate a use case before committing engineering time.

From scope to first delivery

1. Scope confirmation — integration scenarios, target chains, rate-limit expectations, and compliance constraints.
2. Protocol analysis & API design — 2–5 business days to map the Rabby + DeBank + chain-RPC surface into your endpoints.
3. Build and internal validation — 3–8 business days for implementation, unit & integration tests.
4. Docs, samples, and test cases — 1–2 business days to ship OpenAPI, Postman, and runbook.
5. First delivery — typically 5–15 business days; complex multi-chain or webhook flows may extend timelines.

FAQ

What do you need from us to start?

Do you ever touch private keys or seed phrases?

How do you handle compliance?

What if Rabby's API rate limits are too low for our volume?