Initiates settlement of a specific asset leg within a Prime settlement batch. The batch must be confirmed and the leg must be eligible for settlement (check can_settle on the leg).
API Key Permissions Required: Orders and trades - Create & modify orders
curl --request POST \
--url https://api.kraken.com/0/private/SettlePrimeSettlementBatchAsset \
--header 'API-Key: <api-key>' \
--header 'API-Sign: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"nonce": 123,
"batch_id": "B_Y7T2LPVX",
"asset": "BTC"
}
'{
"result": {
"transfer": {
"id": "100",
"attributes": {
"transfer_status": "pending",
"transfer_amount": "1.5",
"transfer_asset": "BTC"
},
"relationships": {
"leg": {
"status": "unsettled",
"asset": "BTC",
"amount": "1.5",
"direction": "incoming",
"can_settle": true,
"settled_at": 123,
"latest_spot_transfer": {}
}
}
}
},
"error": [
"EGeneral:Invalid arguments"
]
}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/SettlePrimeSettlementBatchAsset \
--header 'API-Key: <api-key>' \
--header 'API-Sign: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"nonce": 123,
"batch_id": "B_Y7T2LPVX",
"asset": "BTC"
}
'{
"result": {
"transfer": {
"id": "100",
"attributes": {
"transfer_status": "pending",
"transfer_amount": "1.5",
"transfer_asset": "BTC"
},
"relationships": {
"leg": {
"status": "unsettled",
"asset": "BTC",
"amount": "1.5",
"direction": "incoming",
"can_settle": true,
"settled_at": 123,
"latest_spot_transfer": {}
}
}
}
},
"error": [
"EGeneral:Invalid arguments"
]
}