Creates a new API key with the specified scope and permissions. API keys are used for programmatic access to the Deribit API and can be restricted to specific operations and IP addresses.
The response includes both the API key ID and the secret key. Store the secret securely as it will not be displayed again. You can view the API key details (without the secret) using the list_api_keys method.
๐ Related Articles:
Scope: account:read_write
Describes maximal access for tokens generated with given key. If scope is not provided, its value is set as none.
๐ Related Article: Access Scope
[
"account:read",
"trade:read",
"block_trade:read_write",
"wallet:none"
]Name of key (only letters, numbers and underscores allowed; maximum length - 16 characters)
"TestName"
ED25519 or RSA PEM Encoded public key that should be used to create asymmetric API Key for signing requests/authentication requests with user's private key.
๐ Related Article: Asymmetric API keys
"-----BEGIN PUBLIC KEY-----\nMCowBQYDK2VwAyEAM7FWhKquNqLmTOV4hfYT5r3AjrYiORTT6Tn5HIfFNV8=\n-----END PUBLIC KEY-----"
List of enabled advanced on-key features. Available options:
- restricted_block_trades: Limit the block_trade read the scope of the API key to block trades that have been made using this specific API key
- block_trade_approval: Block trades created using this API key require additional user approval. Methods that use block_rfq scope are not affected by Block Trade approval feature
restricted_block_trades, block_trade_approval