Skip to main content
This is not a traditional drop copy session. Kalshi’s Drop Copy uses a request-response pattern for querying historical execution reports. For a real-time streaming feed, use a Listener Session on KalshiRT instead.
Historical execution-report replay through EventResendRequest (35=U1) requires allowlisting for your user account on both KalshiNR and KalshiDC sessions. Contact institutional@kalshi.com to request access. Requests from accounts that are not allowlisted are rejected with EventResendReject (35=U3), reason 5 (NOT_ENABLED). Allowlisting does not backfill earlier events.
Execution reports are retained for 24 hours. Requests for execution reports 24 hours old or older are best effort and may be rejected. Only ExecutionReport (35=8) messages are returned. Rejects and pending orders (ExecID "-1;-1") are excluded. The 24-hour period includes maintenance periods. Requests for unavailable history are rejected with EventResendReject (35=U3), reason 3.
Resent messages have new FIX sequence numbers, different from their original numbers on the trading session. Use ExecID to reconcile.

EventResendRequest (35=U1)

Request execution reports within a specified ExecID range. Pass ExecIDs exactly as received. Each request replays one ExecID sequence, identified by LastMkt (tag 30), so BeginExecID and EndExecID must come from the same sequence. After a disconnect, send one request per sequence. Example:

EventResendComplete (35=U2)

Sent after all requested events have been resent. A valid range with no matching execution reports for your account completes with ResendEventCount=0.

EventResendReject (35=U3)

Sent when a resend request cannot be fulfilled.