Welcome to the next crypto level
← Nexorena

technology

Kraken unifies transfers between spot and futures accounts

Kraken set November 17 as the date for a common transfer method in its derivatives API. Two legacy endpoints are due to be removed on November 30.

Nexorena Editorial Team

Kraken unifies transfers between spot and futures accounts

One request handles transfers in either direction

Kraken announced in its Exchange API changelog that, starting November 17, the POST /transfer endpoint can move funds between a futures wallet and a Kraken spot wallet. The original date was November 12. The revised timetable moves the change back five days. To specify the direction, an integration puts spot in the source or destination account field.

The documentation says settlement occurs before the response is sent. An integration can use the response to see whether the transfer succeeded without querying a second service to track settlement. This matters to software that performs several operations in sequence based on the balance available. The change applies to internal transfers between linked wallets. Transfers involving the spot wallet are available to futures accounts linked to a Kraken account.

Withdrawal permissions and rate limits still apply

A transfer to or from the spot wallet requires an API key with withdrawal permission. Kraken says each request uses 100 units of the API’s rate-limit budget, compared with 10 units for transfers between futures wallets. That cost is measured in request units. Error handling can distinguish causes, including insufficient funds, an invalid amount or an invalid currency. Transfers between two futures wallets also return more specific reasons when refused.

Kraken is also adding GET /transfer/assets. The endpoint lists assets the account can transfer and the minimum and maximum amounts applicable to transfers involving the spot wallet. It also indicates whether an account linked to a multilateral trading facility can transfer an asset to spot. A call uses two rate-limit units. This lets software adapt the options it presents to the user to the assets and limits of the account.

Integrations need to replace legacy calls by November 30

Kraken plans to remove POST /withdrawal and GET /transfers on November 30. To withdraw funds from a derivatives wallet to spot, the documentation points to POST /transfer with spot as the destination. The legacy GET /transfers endpoint lists only activity from the previous system. Transfers using the new method appear in the account log.

For teams that reconcile balances across wallets, the change affects both the request that starts the movement and the source used to find its record afterward. Kraken’s published schedule allows until November 30 to switch to the new method. Affected integrations can use the account log to confirm their reconciliation follows the path each transfer actually took.

Article sources

Written with love byRyan MitchellMeet this editorial pen name ↗

Explorer Nexorena