Skip to main content
A Session Key is a separate signer that a Deposit Wallet Owner authorizes to trade for a Deposit Wallet. It lets an integration perform routine trading without using the owner’s key. A Session Key cannot withdraw funds from the Deposit Wallet.
Session Keys work only with Deposit Wallets. A dedicated migration flow from Safe Wallets and Proxy Wallets is planned.
A Session Key can be scoped to trade on specific supported venues or all venues:

Authorize a Session Key

The Deposit Wallet Owner authorizes a session signer address with an expiration of 180 days and scoped permissions.
Session Keys are Externally Owned Accounts (EOAs). Keep their private keys secret to prevent unauthorized trading on behalf of your Deposit Wallet.
Authorizing or revoking a Session Key requires a Relayer API key for the Deposit Wallet Owner’s address or a Builder API key.
1

Generate a Session Key

First, generate a fresh EVM keypair for the Session Key.
Store your private key in a secrets manager or another secure key store.
2

Create the Deposit Wallet Owner Client

Then, create a SecureClient with the Deposit Wallet Owner’s private key and either a Relayer API key or Builder API credentials.
In relayerApiKey(), address is the Deposit Wallet Owner’s address.
3

Authorize the Session Key

Finally, call authorizeSessionKey() to authorize your Session Key.
You can also authorize only the desired trading venues with the scopes parameter:

Place an Order

This section shows how to place an order using a Session Key. See Place Orders for the complete order workflow.
1

Create the Session Client

First, create a SecureClient for the Deposit Wallet with the session signer.
2

Place an Order

Then, submit a limit order with the already-selected assetId.
The order buys 10 shares at a price of 0.52 USD per share. See Place Orders for market constraints, order types, and response handling.

Manage Wallet Orders

List and cancel open orders across the Deposit Wallet, whichever signer placed them. The Deposit Wallet Owner and any active Session Key can list them. Only the Deposit Wallet Owner can cancel them.

List Wallet Orders

List all open orders on the Deposit Wallet, or filter by market, outcome, or the signers that placed them.
Call listWalletOpenOrders() on a SecureClient for the Deposit Wallet Owner or a Session Key. Omit filters to list all open orders:
To filter the list, create pages with one of these calls, then iterate as above:
signerAddresses accepts up to 50 signer addresses. For owner orders, use the Deposit Wallet Owner’s signer address, not the Deposit Wallet address. market takes the market’s condition ID. Use assetId to filter by outcome. Filters can be combined.
signerAddress is the signer that placed the order. owner is null when the order’s API key identifier is withheld.

Cancel Wallet Orders

The Deposit Wallet Owner can cancel up to 1,000 orders by ID or every open order on the Deposit Wallet. If a cancellation’s outcome is uncertain, such as after a network error, list the wallet orders before retrying.
Call cancelWalletOrders() on the Deposit Wallet Owner’s SecureClient:
Call cancelAllWalletOrders() to cancel every open order:
Each request returns a cancellation result.

Fetch Session Keys

List the active Session Keys for a Deposit Wallet to see which signers can currently act on its behalf.
Call fetchSessionKeys() on the Deposit Wallet Owner’s SecureClient:

Revoke a Session Key

Revoke a Session Key when an integration no longer needs access or its private key may have been exposed. Revocation prevents further trading by that key and cancels its open orders without affecting orders placed by other Session Keys.
Call revokeSessionKey() on the Deposit Wallet Owner’s SecureClient with the Session Key’s public address:
revokeSessionKey() resolves to void once the Session Key is no longer active in the Wallet Registry. The backend continues the remaining revocation work asynchronously, canceling open orders and finalizing the on-chain transaction.

Session Key Considerations

Configurable shorter Session Key expirations are not currently supported. To end access before 180 days, revoke the Session Key. If you are adding Session Key support to an existing integration, keep these access boundaries in mind: