Build share-card numbers, candles and trade markers for a registered account. Supply up to 20 active instruments and 4 historical fills, with at least one selection. History keys use instrument_id, trade_id and the public fill timestamp in milliseconds. Trade IDs are UInt64 decimal strings; returned IDs omit leading zeroes. Duplicates and explicit null arrays are rejected. Weight is max(10, active + 7 × history).

Responses use Cache-Control: private, no-store. The route is public; valid owner authentication reveals leverage and pnl_percent. Both fields are null for anonymous callers and other accounts. Invalid supplied credentials return 401.

Active snapshots use captured state; history ends after the selected fill. A fill that closes a cycle, fully or by crossing, returns that closed cycle's card. The cycle it opens is served by the active card or by its later fills. PositionCardSnapshot defines valuation, PnL and leverage availability.

Results preserve order within active and history. Only ok items contain snapshot. not_found means no current position or owned fill within history_as_of_at; gateways may have different horizons. history_pending means a known fill or a position needing bootstrap is ahead of completed history, or the self-match index coverage gate is not armed for historical cards; retry with backoff. history_limit means the reconstruction window lacks the opener. resource_limit means a row, memory or chart bound was exceeded. temporarily_unavailable includes deadlines and transient pricing or dependency failures. unavailable includes unsafe accounting, self-matches, backstop transfers, non-fill repairs and legacy multi-leg selections with unknowable fill order.

Candles include the selected minute's aggregate, without a per-fill cutoff inside it. Charts retain the left boundary bucket and at least one hour of context, with at most 22 candles and 256 markers. Unknown accounts and malformed input return 400. Admission and shared dependency failures return 503; retry with backoff. HTTP 413 is reserved for an oversized request body.

{
  "address": "0x1234567890abcdef1234567890abcdef12345678"
}

{
  "active": [
    {
      "instrument_id": 1
    }
  ],
  "history": [
    {
      "instrument_id": 1
    }
  ]
}