Skip to main content
POST
Create API Key

Authorizations

KALSHI-ACCESS-KEY
string
header
required

Your API key ID

KALSHI-ACCESS-SIGNATURE
string
header
required

RSA-PSS signature of the request

KALSHI-ACCESS-TIMESTAMP
string
header
required

Request timestamp in milliseconds

Body

application/json
name
string
required

Name for the API key. This helps identify the key's purpose

public_key
string
required

RSA public key in PEM format. This will be used to verify signatures on API requests

scopes
enum<string>[]

List of scopes to grant to the API key. If the broad write parent scope is included, read must also be included. Child scopes may be granted without the broad parent scope. Defaults to full access (read, write) if not provided.

Scope granted to an API key. Parent scopes grant broad access; for example, read grants all read endpoints and write grants all write endpoints. Child scopes such as read::block_trade_accept, read::portfolio_balance, write::trade, write::transfer, and write::block_trade_accept grant only their specific endpoint group and can be granted without the parent scope.

Available options:
read,
write,
read::block_trade_accept,
read::portfolio_balance,
write::trade,
write::transfer,
write::block_trade_accept
subaccount
integer

If set, restricts the API key to a single sub-account (0-63) that you own. A restricted key may only read and trade on that sub-account; it cannot act on other sub-accounts, transfer funds between sub-accounts, or create sub-accounts. Omit to leave the key unrestricted.

Required range: 0 <= x <= 63

Response

API key created successfully

api_key_id
string
required

Unique identifier for the newly created API key