To configure user access to Kalshi:
- Configure user access on the Exchanges tab:
- Click the Users | Exchanges tab for a user selected in the data grid.
- Click the exchange list drop down arrow, and select Kalshi.
- Configure the following tabs:
- Subscriber Market Data
- Select Allow for All Market Data
- Confirm that the User Agreement is approved.
- Order Routing (Optional)
- Select an SMP Instruction.
- SDK Client Market Data (Required if receiving Kalshi market data through TT Core SDK)
- FIX and SDK Market Data (Required if receiving Kalshi market data through TT FIX applications)
- Subscriber Market Data
- Click Save Changes.
- Assign the user to the Kalshi account on the user’s Accounts tab.
Subscriber Market Data
Click the Subscriber Market Data tab and select Allow for All Market Data.
| # | Field | Description | Required / Optional |
| 1 | Exchanges tab | Opens the user’s exchange settings. | Required |
| 2 | Exchange list | Select Kalshi. | Required |
| 3 | Subscriber Market Data tab | Market data permissions for the user’s TT applications. | Required |
| 4 | Allow | Gives the user Kalshi market data. | Required |
| 5 | Deny | Removes Kalshi market data from the user. | Optional |
| 6 | Sessions | Number of sessions on which the user can receive Kalshi market data at the same time. | Required |
| 7 | Allow All / Deny All | Sets all market data permissions on the tab at once. | Optional |
Market Data Subscription Agreement
Click the Agreements tab and confirm that the Kalshi Market Data Subscription Agreement shows a Status of Approved.

| # | Field | Description | Required / Optional |
| 1 | Agreements tab | Lists the exchange agreements for the user. | Required |
| 2 | Kalshi Market Data Subscription Agreement | The Kalshi subscriber agreement. Kalshi market data is not available until it is approved. | Required |
| 3 | Status | Outstanding or Approved. | Required |
The other columns show the agreement description, mandatory date, expiry date, completed date, and last updated date.
Order Routing with Self-Match Prevention
-
Click the Order Routing tab.
-
For SMP Instruction, select one of the following:
- Cancel Newest: cancels the incoming order and leaves the resting order on the book.
- Cancel Oldest: cancels the resting order and allows the incoming order to continue.
If SMP Instruction is left blank, Kalshi cancels the incoming order.

| # | Field | Description | Required / Optional |
| 1 | Users | Lists the users in your company. Select the user to configure. | Required |
| 2 | Exchanges tab | Opens the user’s exchange settings. | Required |
| 3 | Exchange list | Select Kalshi. | Required |
| 4 | Order Routing tab | Order settings for the user on Kalshi. | Optional |
| 5 | SMP Instruction | Kalshi self-match prevention. Cancel Newest cancels the incoming order. Cancel Oldest cancels the resting order. When blank, Kalshi cancels the incoming order. | Optional |
| 6 | Client Can Override | Allows or prevents the user from changing the value when placing orders. | Optional |
| 7 | Max Order Rate Per Connection (orders/sec) | Limits how many orders per second the user can send on each Kalshi connection. | Optional |
SDK Client Market Data
Note: Required if receiving Kalshi market data through TT Core SDK
Click the SDK Client Market Data tab to allow or deny access to the market data groups available at the exchange for TT .NET SDK Client Side trading applications.
If you click Allow to enable a market data group, configure the Sessions field as follows:
- If using only TT .NET SDK Client Side application keys, then set Sessions equal to the number of application keys you plan to run concurrently.
- If using only TT .NET SDK Client Side – Non-display application keys, then set Sessions equal to “0” and check the Non-display checkbox, which indicates the market data is for non-display purposes (e.g., black-box algorithm, automated program for calculating P/L, etc.) as defined by the exchange.
- If using both TT .NET SDK Client Side and TT .NET SDK Client Side – Non-display application keys, then set Sessions equal to the number of TT .NET SDK Client Side application keys that you plan to run concurrently and check the Non-display checkbox.
If you are distributing the market data externally (e.g., to users outside of your company), check the External Distribution checkbox.
Note: Any product groups that are disabled have not been authorized for your company. Please contact a Trading Technologies representative to enable them.
FIX and SDK Server Market Data
Note: Required if receiving Kalshi market data through TT FIX applications
Click the FIX and SDK Server Market Data tab to allow or deny access to the market data groups available at the exchange for TT FIX, TT .NET SDK Server Side, and TT Core SDK trading applications.
If you click Allow to enable a market data group, click Quantity to set the number of users viewing the market data behind the FIX feed or the number of TT .NET SDK Server Side or TT Core SDK applications using the data concurrently.
If the FIX feed or SDK server-side trading application is for non-display purposes (e.g., black-box algorithm, program for calculating P/L, etc.) as defined by the exchange, click Allow to enable the market data group, set the Quantity, and check Non-display.
If you are distributing the market data externally (e.g., to users outside of your company), check the External Distribution checkbox.
Note: Any product groups that are disabled have not been authorized for your company. Please contact a Trading Technologies representative to enable them.
If Allow is enabled, click Quantity to set the number of simultaneous FIX applications viewing the market data behind the FIX feed.
User Kalshi Account Access
Assign the user to the Kalshi account on the user’s Accounts tab.
Setup > Users

| # | Field | Description | Required / Optional |
| 1 | Setup | Opens TT Setup. | Required |
| 2 | Users | Lists the users in your company. Select the user to configure. | Required |