Get the status of the last allocation request.
Requires either the Earn Funds or Query Funds API key permission.
(De)allocation operations are asynchronous and this endpoint allows client to retrieve the status of the last dispatched operation. There can be only one (de)allocation request in progress for given user and strategy.
The pending attribute in the response indicates if the previously
dispatched operation is still in progress (true) or has successfully
completed (false). If the dispatched request failed with an error, then
HTTP error is returned to the client as if it belonged to the original
request.
Following specific errors within Earnings class can be returned by this
method:
EEarnings:Insufficient funds:Insufficient funds to complete the (de)allocation requestEEarnings:Above max:The allocation exceeds user limit for the strategyEEarnings:Above max:The allocation exceeds the total strategy limitEEarnings:Below min:(De)allocation operation amount less than minimumcurl --request POST \
--url https://api.kraken.com/0/private/Earn/AllocateStatus \
--header 'API-Key: <api-key>' \
--header 'API-Sign: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"nonce": 30295839,
"strategy_id": "ESRFUO3-Q62XD-WIOIL7"
}
'{
"error": [],
"result": {
"pending": false
}
}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.
curl --request POST \
--url https://api.kraken.com/0/private/Earn/AllocateStatus \
--header 'API-Key: <api-key>' \
--header 'API-Sign: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"nonce": 30295839,
"strategy_id": "ESRFUO3-Q62XD-WIOIL7"
}
'{
"error": [],
"result": {
"pending": false
}
}