Credentials & Wallets

Connect your exchange accounts and set up your Sequence Wallet for DEX trading.

Sequence Wallet

Your Sequence Wallet is an MPC-secured wallet that lets you trade on-chain (DEX) via the API without keeping your browser open. It's automatically provisioned when you connect MetaMask on the dashboard.

How it works

1. Connect MetaMask on the dashboard (Settings → Wallets)
2. Your Sequence Wallet is auto-provisioned in the background (~5 seconds)
3. Fund it — send ETH (for gas) and USDC (for trading) from MetaMask to your Sequence Wallet address
4. Trade via API — submit orders without wallet_id; they auto-route to your Sequence Wallet
5. Withdraw anytime — send funds back to your MetaMask via the dashboard or API

List Wallets

Lists on-chain wallets (EVM/Solana) registered for DEX trading.

Returns all DEX wallets for the authenticated user.

{
  "wallets": [
    {
      "wallet_id": "turnkey:0x7f3a...d21e",
      "address": "0x7f3a...d21e",
      "scope": "dex",
      "role": "trading",
      "signer_backend": "turnkey",
      "status": "ready",
      "can_trade_dex": true,
      "can_trade_api": true
    },
    {
      "wallet_id": "connected:0x082a...c859",
      "address": "0x082a...c859",
      "scope": "dex",
      "role": "connected",
      "signer_backend": "connected",
      "status": "ready",
      "can_trade_dex": false,
      "can_trade_api": false
    }
  ]
}

Get Trading Wallet

Returns the trading (Sequence Wallet) details. Alias: GET /v1/wallets/default.

Create Trading Wallet Manually

Manually provision a Sequence Wallet. This is normally done automatically when you connect MetaMask, but you can also trigger it via API.

{
  "label": "My Trading Wallet"
}

Returns 409 if a trading wallet already exists or is being provisioned.

Fund Your Sequence Wallet

Send tokens to your Sequence Wallet address (shown in GET /v1/wallets). You need:

• ETH for gas (~0.001 ETH on Arbitrum, ~$2)
• USDC for the actual trades

You can fund from the dashboard (Settings → Wallets → Fund) or by sending a standard transfer from any wallet.

Withdraw

Send tokens from your Sequence Wallet back to an external address.

{
  "chain": "arbitrum",
  "token": "USDC",
  "amount": "100.0",
  "recipient": "0x082a74ff138843b60eda88f131c54054c96ac859"
}

Order Routing

When you submit a DEX order via POST /v1/orders:

If no Sequence Wallet exists, the API returns NO_TRADING_WALLET (404). If it's still being provisioned, you get TRADING_WALLET_NOT_READY (409).

List Connected Venues

List venues you have credentials for.

Response

{
  "venues": ["kraken", "coinbase", "binance", "kalshi", "polymarket"]
}

Set Credentials

Add or update credentials for a venue. Overwrites any existing row for (client, venue).

Path Parameters

Request Body (Kraken / Binance / Bitget / Crypto.com)

{
  "api_key": "your-api-key",
  "api_secret": "your-api-secret"
}

Request Body (Coinbase)

Coinbase requires additional fields:

{
  "api_key": "your-api-key-id",
  "api_secret": "-----BEGIN EC PRIVATE KEY-----\n...\n-----END EC PRIVATE KEY-----",
  "passphrase": "optional-passphrase"
}

Request Body (Kalshi)

Kalshi uses an API key ID + RSA private key. Orders are signed with RSA-PSS over SHA-256.

{
  "api_key": "dc9d0cd5-076a-4ea8-b406-1847279dac4b",
  "api_secret": "-----BEGIN RSA PRIVATE KEY-----\nMIIE...\n-----END RSA PRIVATE KEY-----"
}

• api_key = the Kalshi API key ID (UUID shown in the Kalshi dashboard).
• api_secret = the full PEM of the paired private key. Both PKCS#1 (BEGIN RSA PRIVATE KEY) and PKCS#8 (BEGIN PRIVATE KEY) are accepted.

Request Body (Polymarket)

Polymarket orders are EIP-712 signed client-side from an EVM signer key. Sequence derives the CLOB L2 credentials from that signer on first use (calling Polymarket's /auth/derive-api-key under the hood), so you only need to supply the signer material in extra_json:

{
  "api_key": "",
  "api_secret": "",
  "extra_json": {
    "signer_private_key": "0xyour-32-byte-private-key",
    "proxy_address": "0xoptional-proxy-wallet-address",
    "builder": "0xoptional-builder-code-address"
  }
}

Response

{
  "venue": "kalshi",
  "status": "stored"
}

Delete Credentials

Remove credentials for an exchange.

Response

{
  "venue": "kraken",
  "deleted": true
}

Get Positions

Balances and positions are unified into one endpoint. See Positions — use GET /v1/positions?kinds=fiat,crypto for the old balances() shape.

Fee Tiers

Your per-venue maker/taker fee tier is fetched automatically in the background whenever you POST /v1/credentials/{venue} — the edge probes the venue's fee endpoint (where supported) and caches the result. The cached tier feeds the SOR cost model and TCA reports; it isn't exposed as a standalone read endpoint. If the probe fails (API lacks the permission, venue doesn't expose it), SOR falls back to hardcoded per-venue defaults.

API Key Management

Sequence uses two key prefixes to distinguish live and sandbox environments:

The key prefix determines the mode automatically on the server side. All API endpoints respect this: a seq_test_ key can only interact with sandbox infrastructure (sandbox edges, sandbox algo deployments), and a seq_live_ key only interacts with live infrastructure. The two modes are fully isolated - same client, same symbol, different modes.

List API Keys

Returns all API keys for the authenticated client as a bare array.

[
  {
    "id": "a1b2c3d4-...",
    "key_prefix": "seq_live_94b98a3c",
    "label": "production",
    "is_active": true,
    "last_used_at": "2026-02-28T12:00:00Z",
    "created_at": "2026-01-15T08:00:00Z"
  }
]

Create API Key

{
  "label": "my-new-key",
  "sandbox": false
}

Response:

{
  "id": "a1b2c3d4-...",
  "key_prefix": "seq_live_f8a2b1c0",
  "raw_key": "seq_live_f8a2b1c0..."
}

To create a sandbox key for paper trading:

{
  "label": "paper-trading",
  "sandbox": true
}

Returns a seq_test_ key:

{
  "id": "b2c3d4e5-...",
  "key_prefix": "seq_test_a1b2c3d4",
  "raw_key": "seq_test_a1b2c3d4..."
}

Delete API Key

Deactivates the key. Cannot delete the key you're currently authenticated with.

Rotate API Key

Atomically deactivates the old key and creates a new one with the same label. Returns the new key:

{
  "id": "new-key-uuid",
  "key_prefix": "seq_live_d2e4f6a8",
  "raw_key": "seq_live_d2e4f6a8..."
}

Venue Setup Guides