Partner API

​

Why create your own users

• Per-user balances and risk. Funds, open orders, positions and settlements are separate for every user, so one user’s activity never touches another’s.
• Per-user history. Orders, fills, bets and the ledger come back per account, with no attribution layer to maintain.
• You stay in control. You choose which permissions each user’s API key gets, and you keep the key. SX Bet never sees a user’s private key.
• No separate sign-up. Users are created from your backend in one call. They don’t need an sx.bet login.
• Externally owned accounts. The signature must recover to the user’s address, from eth_signTypedData_v4 on a standard externally owned account. Contract-wallet signatures (EIP-1271) are not accepted.
• Server-side integration. Anything done on behalf of the user is done server side with the API key, which gives you complete control over your front-end

​

How it works

​

Becoming a partner

​

Create a user

import { privateKeyToAccount } from "viem/accounts";

const API = "https://api.toronto.sx.bet";
const partnerKey = process.env.SX_PARTNER_KEY!;
const wallet = privateKeyToAccount(process.env.USER_PRIVATE_KEY as `0x${string}`);

// 1. The statement to sign
const attestation = await fetch(
  `${API}/partner/attestation?address=${wallet.address}`,
  { headers: { "x-sx-api-key": partnerKey } }
).then((r) => r.json());
const { domain, types, primaryType, message } = attestation.data;

// 2. The user's wallet signs it
const signature = await wallet.signTypedData({
  domain,
  types,
  primaryType,
  message: { ...message, partnerId: BigInt(message.partnerId) },
});

// 3. Create the user
const created = await fetch(`${API}/partner/users`, {
  method: "POST",
  headers: { "x-sx-api-key": partnerKey, "content-type": "application/json" },
  body: JSON.stringify({
    address: wallet.address,
    userEmail: "trader+1324@yourplatform.com",
    apiKeyPermissions: {
      orders: ["read", "create", "cancel"],
      account: ["read"],
      wallet: ["read", "admin"],
    },
    signature,
  }),
}).then((r) => r.json());

// 4. Store this now: it is shown only once
const userKey = created.data.apiKey.key;

​

After a user is created

1. Wait for the proxy wallet. The create response reports the deployment status in proxyDeployment.status:
   • SUCCESS: deployed, carry on.
   • PENDING: a deployment is running. Don’t start another; poll GET /partner/users until the user’s proxyDeployed is true.
   • FAILED or NOT_STARTED: call POST /user/deploy-proxy with the user key, then poll the same way.
2. Fund it. Send funds to the user’s proxyWalletAddress only after deployment completes. See Funding.
3. Trade. Place orders with POST /orders-v3. Each order is signed by the user’s wallet, as for any account.

​

View your users

​

Rate limits

​

Managing users

​

Related