Économie
Kraken adds spot-to-derivatives transfers to its API
The November 12 release lets linked accounts move funds between a futures wallet and their spot wallet through a single API endpoint. Two legacy endpoints are due to be removed on November 30.

One endpoint for spot and derivatives
Kraken says in its November 12 release notes that POST /transfer can now move funds between a futures wallet and the spot wallet of a linked Kraken account. The calling software specifies spot as the source or destination account. That covers transfers in both directions, from the spot wallet to derivatives and from derivatives to the spot wallet. Kraken’s status log marked maintenance of its derivatives platform complete at 12:48 a.m. Paris time on November 12.
According to the documentation, the transfer settles before the interface sends its response. Client software can therefore process the result in the same request, without polling another endpoint to check whether that particular transfer has completed. Movements made using the new endpoint appear in the account log. Integrations that reconcile their operations against Kraken records can find those movements in the log, while the old transfers list remains limited to the legacy system.
Spot transfers have separate permissions and limits
Transfers to or from spot require an API key with withdrawal permission. Kraken restricts these transfers to linked accounts and charges 100 rate-limit units, compared with 10 for a transfer between two futures wallets. The difference applies to the interface’s request budget. An integration therefore needs to distinguish a transfer within derivatives from a move to or from spot when calculating how many requests it can send.
Kraken has also added GET /transfer/assets. The endpoint lists the assets an account can transfer, minimum and maximum amounts for a transfer involving spot, and whether an MTF account is allowed to transfer the asset to spot. A call costs two rate-limit units. The release notes distinguish several reasons for failure, including insufficient funds and invalid amounts, units, or currencies. A detailed response lets software distinguish a refusal due to insufficient funds from a request that needs correcting.
Two legacy endpoints are due to go on November 30
The schedule calls for the removal of POST /withdrawal and GET /transfers on November 30, 2026. For a move to the spot wallet, Kraken points to POST /transfer with spot as the destination. To track transfers made through the new endpoint, Kraken points to the account log. The old history therefore remains relevant for transactions made before the change, while reconciliation of new movements needs to account for their different location.
The update also provides more specific errors for transfers between derivatives wallets. Before the change, different refusals could return the same insufficient-funds reason. Kraken says the interface now identifies problems including an invalid amount or currency, an account that cannot be found, or an account that cannot be accessed. The transition to the new endpoints therefore changes how software initiates transfers, reconciles records, and identifies failures.
