Help
API permissions, exactly
Kraken Derivatives keys have two relevant switches: General API and Withdrawal API. PERP KING asks for the smallest pair that can do the job, and then calls only the endpoints that job needs.
Kraken's two switches
This is the derivatives key, documented by Kraken in How to create an API key for Kraken Derivatives (last updated 9 August 2025). It is not the spot key screen, which has a different list of checkboxes such as Modify Orders and Withdraw Funds.
| Switch | Choices Kraken offers | What Kraken says |
|---|---|---|
| General API | No Access, Read Only, Full Access | Full Access allows the endpoints excluding digital-asset withdrawals. Read Only allows endpoints that do not write. |
| Withdrawal API | No Access, Full Access | Full Access allows digital-asset withdrawals. No Access does not. |
Trading and withdrawing are separate. A key can have General API set to Full Access and still have Withdrawal API set to No Access. That is the LIVE combination. There is no third General API choice labelled trade-only.
What PERP KING actually calls
| Key | Stored only if you attest | Requests sent |
|---|---|---|
| Read-only | Read-only, and no withdrawal | Account, positions, open orders and fills |
| Trade | Can trade. Do not enable withdrawal or transfer. PERP KING does not verify that switch. | Place an order. Cancel an order. |
Place and cancel cover entries, reduce-only stops, and exits. They do not cover withdrawals, deposits, transfers, or wallet moves. Those paths are rejected in the customer integration before any request is sent.
Kraken does not expose a call that reports whether the withdrawal switch is on. The attestation is required because the key material alone does not prove it. If you are unsure, delete the key at Kraken and create a new one with Withdrawal API set to No Access.
The steps for the other five integrations are not this Kraken screen. The checklist that names each one is on API permissions.
What not to connect
- A spot API key. It is a different API and will not run this integration.
- Any key with Withdrawal API set to Full Access.
- Your Kraken password, or a two-factor code. Those are never requested.
- A key you also use for something that needs withdrawal. Use a dedicated key.
The connection steps are on Connect Kraken. How the key is stored is on Security.
Questions
Why does LIVE need Full Access if it only sends orders?
Because that is the Kraken Derivatives choice that can write orders. Kraken states that this General API level still excludes digital-asset withdrawals. Withdrawal API must be set to No Access as well. PERP KING then limits itself to placing and cancelling orders.
Can PERP KING withdraw if I make a mistake on the key?
The integration has no withdrawal, deposit or transfer request. Those paths are refused before a network call. You should still set Withdrawal API to No Access so the key itself cannot be used that way.
Sources
Figures in this section are Kraken's, from the documents linked below. They are not PERP KING settings, and Kraken can change them. Clients in the EEA should use the specification Kraken links for that region.
- How to create an API key for Kraken Derivatives — Kraken, last updated 9 August 2025
- Send order — Kraken Futures REST API
Continue
Put PERP KING to work — inside your limits.
Free during the private beta, approved individually. No card, no subscription. Your capital stays in your own exchange account.