Skip to content

Getting Started

1. Register as a Builder

Contact the Parti team to register. You'll receive:

  • API Key (bld_...) — identifies your application
  • API Secret (hex, 32 bytes) — used to sign requests. Store securely. Cannot be retrieved again.

2. Create User Keys

When a user signs up on your platform, create a trading keypair:

curl -X POST ${SIGNER}/v1/keys \
  -H "X-Api-Key: ${API_KEY}" \
  -H "X-Signature: ${HMAC}" \
  -H "X-Timestamp: ${TIMESTAMP}" \
  -H "Content-Type: application/json" \
  -d '{"user_id": "your-internal-user-id"}'

Response:

{
  "user_id": "your-internal-user-id",
  "public_key": "7yQ3mH9a..."
}

The public_key is the user's trading address. Store the mapping.

3. Fund the User

Get a deposit address:

curl -X POST ${SIGNER}/v1/deposit/address \
  -H "X-Api-Key: ${API_KEY}" \
  -d '{"user": "7yQ3mH9a...", "chain": "solana"}'

Have users send USDC to the returned address.

4. Place Orders

curl -X POST ${SIGNER}/v1/submit \
  -H "X-Api-Key: ${API_KEY}" \
  -H "X-Signature: ${HMAC}" \
  -H "X-Timestamp: ${TIMESTAMP}" \
  -H "Content-Type: application/json" \
  -d '{
    "user": "7yQ3mH9a...",
    "market_id": "abc123...",
    "side": "buy",
    "outcome": "yes",
    "price": 6500,
    "size": 100,
    "order_type": "gtc",
    "nonce": 1,
    "fee_bps": 100
  }'

The fee_bps is your builder fee (1% in this example). It's charged on fills and sent to your wallet.

5. View Your Revenue

curl -X POST ${SIGNER}/v1/trades \
  -H "X-Api-Key: ${API_KEY}" \
  -H "X-Signature: ${HMAC}" \
  -H "X-Timestamp: ${TIMESTAMP}" \
  -H "Content-Type: application/json" \
  -d '{"limit": 100}'

Response includes total_builder_fees across all your users' trades.