Skip to content

Trading

Order attribution

Planned

Order attribution tags every order you submit with a builder identifier. SatoriEx uses these tags to credit volume to the integration that originated the trade.

Attribution wiring is not live yet

The `X-Builder-Code` header and `builder_code` body field below describe the planned contract. The order matcher does not yet read either one โ€” submit them if you like, but volume will not be credited until the program ships. Watch the changelog for activation date.

What gets credited

Tagged orders contribute to your builder volume regardless of who clicks the trade button on your surface.

  • Filled volume โ€” counted toward tier thresholds and fee-share calculations.
  • Trade count โ€” surfaced on your builder dashboard and the public leaderboard.
  • User cohort โ€” referred users tagged at registration plus orders tagged at trade time.

How to tag an order

Send your builder code either in the X-Builder-Code header (preferred) or in the order body. The header form survives proxy hops cleanly; the body form is convenient for clients that cannot set custom headers.

POST /api/v1/orders
Authorization: Bearer $SATORIEX_TOKEN
Content-Type: application/json

{
  "market_id": "MKT_ID",
  "outcome_id": "OUT_ID",
  "side": 1,
  "price": 4200,
  "quantity": 100
}

// side: 1 = buy, 2 = sell (int8)
// price: basis points where 10000 = 100% probability ($1.00), e.g. 4200 = 42%
// quantity: number of shares (integer)

If both forms are present and disagree, the body value wins. Use only one to avoid confusion.

Prices are in basis points (BPS) where 10000 = 100% probability ($1.00). Quantities are in shares (integer units).

Rules

  • Tags are immutable once an order is accepted โ€” you cannot retag a resting order.
  • Self-trades (your own retail user against your own resting orders) are rejected and never credited.
  • Suspicious volume โ€” wash patterns, circular trading โ€” is excluded from tier calculations.
  • An order without a builder code is just an ordinary order; nothing breaks.

Attribution is planned, not yet live

These endpoints are part of the planned builder program. Sending the X-Builder-Code header today is harmless but volume will not be credited until the program activates. Watch the changelog for the activation date.