Retrieves the client permissions for the OTC Portal.
API Key Permissions Required: Funds permissions - Query and Funds permissions - Deposit
curl --request POST \
--url https://api.kraken.com/0/private/CheckOtcClient \
--header 'API-Key: <api-key>' \
--header 'API-Sign: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
"nonce": 123
}'{
"error": [
"EGeneral:Invalid arguments"
],
"result": {
"permissions": [
"<string>"
]
}
}Documentation Index
Fetch the complete documentation index at: https://kraken-sandbox.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
The "API-Key" header should contain your API key.
Authenticated requests should be signed with the "API-Sign" header, using a signature generated with your private key, nonce, encoded payload, and URI path.
This schema represents the request body for checking an OTC client's status. No request body is required as the client information is typically passed through authentication headers.
Nonce used in construction of API-Sign header
curl --request POST \
--url https://api.kraken.com/0/private/CheckOtcClient \
--header 'API-Key: <api-key>' \
--header 'API-Sign: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
"nonce": 123
}'{
"error": [
"EGeneral:Invalid arguments"
],
"result": {
"permissions": [
"<string>"
]
}
}