Skip to Content

Connecting to Kraken

To connect Kraken to JetScalp, create an API key in your Kraken account and enter it in the connection settings.

Kraken issues a key pair:

  • API Key — the public API key identifier.
  • Private Key — the secret key used to sign requests.

In JetScalp the Kraken connection has two sections: Spot (spot trading) and Futures (multi-collateral perpetual PF_ contracts on the Flex account; JetScalp does not trade other Kraken futures). They use different API keys: spot and derivatives have separate APIs, and a Spot key does not work for Futures, and vice versa. To trade both spot and futures, create two keys and enter each one in its own section. Kraken issues a Futures key as a Public Key and Private Key pair.

Official guides: spot key  and derivatives key .

1.Open API key management

Sign in to Kraken Pro , open the account menu (the profile icon in the upper-right corner) and go to Settings → API. Spot and futures keys are created in different sections; section names and button locations depend on the version of the Kraken interface.

2.Create an API key

  • Key for the Spot section — in the API section, click Create API key.
  • Key for the Futures section — open the API section in your Kraken Derivatives account settings and create a new key.

Enter a name for the key, for example JetScalp. The name must be unique among the account’s API keys.

To trade futures, your account must have access to Kraken Futures. Futures availability depends on your country of residence and account status.

3.Configure permissions

Kraken Spot

Enable:

  • Query Funds
  • Query Open Orders & Trades
  • Query Closed Orders & Trades
  • Modify Orders
  • Cancel/Close Orders
  • WebSocket interface
  • Deposit Funds
  • Withdraw Funds

The WebSocket interface permission is required: it provides the WebSocket API authentication token; without it JetScalp cannot get the private stream and the connection is not established. Do not enable other permissions — the key needs only those listed above.

Kraken Futures

GroupValue for JetScalp
General APIFull Access
Withdrawal APINo Access

Full Access grants access to all endpoints except digital asset withdrawals; Read Only is not enough for trading.

Important: JetScalp does not need the withdrawal permissions (Withdraw Funds for Spot and Withdrawal API for Futures) — do not enable them.

Permission names may differ depending on the version of the Kraken interface.

4.Configure additional options

When creating a Spot key, Kraken offers additional settings:

  • Key Expiration — the key’s validity period. If you set it, the connection stops working once the period ends, and you will need a new key.
  • Custom Nonce Window — leave the default value.
  • Query Start/End Date/Time — do not restrict it: JetScalp loads order and trade history.

Do not enable two-factor authentication (2FA) for the API key itself. Kraken lets you add it to an existing key on the Security page, but then every request must include a one-time code, and JetScalp does not send such codes. 2FA for signing in to your Kraken account stays enabled.

5.Restrict access by IP

For a Spot key, Kraken offers the IP Address Restriction option: the key works only from the specified IP addresses. Enter the IP address JetScalp connects to Kraken from. If JetScalp works through a proxy, enter the IP address Kraken sees when you connect through that proxy.

If you do not know which IP to enter, find it out first: with a wrong IP, Kraken rejects the connection.

6.Confirm creation and save the key

Click Generate key and, if Kraken asks, complete the security check. Kraken shows the API Key (the Public Key for a Futures key) and the Private Key. Copy both keys right away.

Important: Kraken shows the Private Key of a Futures key only once. If it is lost, delete the key and create a new one.

7.Add the connection in JetScalp

Open Settings Settings → Connections, click Add connection below the connection list and click the tile Kraken. The connection appears in the list, and its settings appear on the right.

Fill in the connection settings:

FieldValue
NameThe connection name in the list. By default it is the exchange or broker name; you can change it.
ProxyA proxy from the list or None. See Proxy settings.

Kraken has two markets, so the connection settings have two sections — Spot and Futures, each with its own switch and state. Turn off the section of a market you do not trade: JetScalp will not connect to it, and the section's fields are kept.

Fill in the fields in each section:

Spot:

FieldValue
API KeyThe API Key of the Spot key.
Private KeyThe Private Key of the Spot key.

Futures:

FieldValue
Public KeyThe Public Key of the Futures key.
Private KeyThe Private Key of the Futures key.

If you trade only one market, fill in its section and turn the other one off.

8.Turn on the connection and check

Turn the connection on with the switch on the right of its row in the list. The state appears under the connection name: first connecting…, then connected. If the connection fails, the error text appears there — the full text is shown in the tooltip and in the header of the connection settings. For all states, see Connections.

Check that:

  • Kraken is connected.
  • The account balance is shown.
  • Open positions are shown.
  • Orders are placed and canceled.

If the connection does not work

Invalid API Key or Private Key

Check that both keys are copied completely and without extra spaces. The Private Key field takes the Private Key, not the API Key or Public Key.

The message “Kraken Spot: the API secret must be Base64 — copy it from Kraken unchanged.” (or the same for “Kraken Futures”) means the Private Key field does not hold a Base64 key: it is copied incompletely, with extra characters, or it is a different value. Copy the Private Key from Kraken again.

Spot key used for futures (or vice versa)

The keys are not interchangeable: the Futures section needs a key from the Futures section of Kraken, the Spot section needs a key from the spot API section.

Insufficient permissions

If the connection is not established or orders are not placed, check the permissions: for Spot, all of those from step 3, including WebSocket interface; for Futures, General API set to Full Access.

2FA enabled for the key

If two-factor authentication has been added to the API key, Kraken rejects JetScalp’s requests. Create a key without key-level 2FA.

Key used in another program

Kraken checks that the number (nonce) of each request made with a key is greater than the previous one. If another program or bot uses the same key at the same time, errors such as EAPI:Invalid nonce may occur. Create a separate key for JetScalp.

IP restriction

If the key has an IP restriction, make sure the IP address of the computer or proxy is in the allowed list.

API key expired or deleted

Open Kraken → Settings → API and make sure the key exists and has not expired. Delete a compromised key and create a new one.

Security

Never share your API Key, Public Key and Private Key — not in chats or Telegram, not with support, not on forums, in screenshots or public repositories.

JetScalp does not need the withdrawal permission — do not enable it.

If the key may have reached anyone else, delete it in Kraken right away and create a new one.

Last updated on