Backed Finance API – Integration Guide

Who this is for

  • Clients (authenticated): organizations with a Backed account who need programmatic access to their sweeping wallet addresses, issuance/redemption flows, and account‑specific data.

  • Integrators (public data): market data consumers who need prices of underlyings and token state (e.g., current multipliers). Some public endpoints may require authentication in the future.

Environments & versioning

  • Base URL: https://api.backed.fi

  • OpenAPI/Swagger: https://api.backed.fi/api-docs/

  • Versioning: All endpoints are under /api/v1/*.

  • Rate limits: Public endpoints – 10 requests/minute; Client endpoints – 60 requests/minute.

Authentication

Clients (authenticated endpoints)

  • Header: X-API-KEY: <your_api_key>

  • How to obtain: Backed App → Settings → API → generate key.

  • Send with every request to client endpoints.

Integrators (public endpoints)

  • No auth required at the moment. (Subject to change; plan for adding an API key header without code changes.)

Backed Finance Issuance & Redemption Model

Backed assigns each primary client a dedicated sweeping address per token. Backed continuously monitors these addresses. Whenever a deposit is detected from a registered client wallet:

  • Issuance: If the deposit is in a supported stablecoin, Backed processes the issuance automatically, delivering the corresponding token to the client.

  • Redemption: If the deposit is of any supported xStocks token, Backed processes the redemption automatically, delivering the stablecoin proceeds to the client.

This automation ensures a seamless experience where clients simply send assets to their assigned sweeping address, and Backed handles the full on-chain and off-chain interaction process.

Quick starts

1) Clients: fetch your sweeping wallets (per network)

Use this to obtain the addresses for issuance and redemption on a given network.

Request

GET /api/v1/client/sweeping-wallets/{network}
Host: api.backed.fi
X-API-KEY: <YOUR_API_KEY>

Path params

  • network – see Swagger documentation for available values.

Successful response (example shape)

{
  "issue": [
    {
      "address": "0x...", 
      "token": {
        "name": "Backed <Product>",
        "symbol": "<TOKEN>",
        "networks": ["Ethereum", "Polygon", "Solana"]
      }
    }
  ],
  "redeem": { "address": "0x..." }
}

cURL

curl -s \
  -H "X-API-KEY: $CLIENT_API_KEY" \
  https://api.backed.fi/api/v1/client/sweeping-wallets/Solana

2) Clients: retrieve your trade history

Use this to fetch your past issuance and redemption activity, including transaction details and status.

Request

GET /api/v1/client/trades
Host: api.backed.fi
X-API-KEY: <YOUR_API_KEY>

Query params (optional)

  • limit – number of results per page (default: 20, max: 100)

  • offset – pagination offset (default: 0)

  • status – filter by trade status (e.g., completed, pending)

  • type – filter by trade type (issue or redeem)

  • from_date – filter trades from this date (ISO 8601 format)

  • to_date – filter trades up to this date (ISO 8601 format)

Successful response (example shape)

{
  "trades": [
    {
      "id": "string",
      "type": "string",
      "tradeDate": "string",
      "baseUnits": 0,
      "multiplier": 0,
      "settlementDate": "string",
      "assetPair": "string",
      "tokenSymbol": "string",
      "quantity": 0,
      "shares": 0,
      "pricePerToken": 0,
      "fee": {
        "amount": 0,
        "currency": "string"
      },
      "totalCost": 0,
      "buySide": "string",
      "sellSide": "string",
      "blockchainTransactionWithdrawHash": "string",
      "blockchainTransactionDepositHash": "string",
      "network": "string",
      "depositWallet": "string",
      "status": "string"
    }
  ],
  "pagination": {
    "total": 42,
    "limit": 20,
    "offset": 0
  }
}

cURL examples

# Get all trades
curl -s \
  -H "X-API-KEY: $CLIENT_API_KEY" \
  https://api.backed.fi/api/v1/client/trades

# Get only completed redemptions from the last 30 days
curl -s \
  -H "X-API-KEY: $CLIENT_API_KEY" \
  "https://api.backed.fi/api/v1/client/trades?type=redeem&status=completed&from_date=2024-02-15T00:00:00Z"

# Paginate through results (page 2, 50 results per page)
curl -s \
  -H "X-API-KEY: $CLIENT_API_KEY" \
  "https://api.backed.fi/api/v1/client/trades?limit=50&offset=50"

Notes

  • Trade history includes both successful and failed transactions

  • The multiplier field shows the multiplier that was active at the time of the trade

  • Use pagination for large result sets to avoid timeouts

  • Timestamps are in UTC (ISO 8601 format)

3) Integrators: get the underlying price (collateral quote)

Use this to display the current price of the underlying security for a Backed token.

Request

GET /api/v1/collateral/quote?symbol=AAPL
Host: api.backed.fi

Query params

  • symbol – the underlying share symbol (e.g., AAPL, NVDA, etc.).

cURL

curl -s "https://api.backed.fi/api/v1/collateral/quote?symbol=AAPL"

Notes

  • This endpoint returns the underlying collateral price, not the on‑chain token price.

  • Supports fetching multiple quotes at once by passing a comma-separated list of symbols (e.g. ?symbol=COIN,CRCL,GOOGL,NVDA,TSLA,AAPL).

4) Integrators: get the current multiplier for a token

Backed tokens like xStocks are rebasing instruments. A token's multiplier changes after corporate actions (dividends, splits, reverse splits). Your UI should use the latest multiplier to display the correct exposure/value per token.

  • Locate the Multiplier Updates endpoint in Swagger (Tokens section) and query by token symbol and network.

  • The response includes the timeline of multiplier changes and their activation timestamps. Use the latest active (or scheduled) update for pricing/valuation.

Tip: cache multiplier data and refresh on schedule. Around activation timestamps, pause downstream actions briefly to avoid edge‑case mismatches.

Multiplier primer (what to show vs. what to sign)

  • Display/UI: always scale by the current multiplier to show the correct exposure/value.

  • Signing/transactions: always use raw token amounts (not scaled UI amounts).

  • Activation time: multiplier updates are published in advance with a future Unix timestamp. The new multiplier becomes effective exactly at that time.

Example (conceptual)

  • User holds 100.0 AAPLx.

  • Current multiplier m = 1.05 → effective claim ≈ 100 × 1.05 = 105 units of the underlying.

Common integration patterns

Wallet & operations (clients)

  1. Fetch sweeping wallets per network → show the deposit/return addresses.

  2. Issue: send a supported stablecoin from a registered wallet to the issuance address of a token you'd like to issue.

  3. Redeem: send the token to be redeemed to the redemption address on the relevant chain.

  4. Track activity: use the trades endpoint to monitor your issuance/redemption history and reconcile transactions.

Pricing & portfolio (integrators)

  1. Fetch collateral quote for the underlying (by symbol).

  2. Fetch multiplier updates for the token & network; pick the latest active.

  3. Compute display value = token_balance × multiplier × underlying_price.

Change management

  • Public endpoints may require authentication in the future. Build your client so that adding X-API-KEY is a non‑breaking change.

  • Multipliers are scheduled in advance; consider a short safety window (e.g., ±15 minutes) around activation for trading/settlement systems.

Support

PreviousDividends & Stock Splits Technical OverviewNextLegal and Regulatory Overview

Last updated