Connecting to Coinbase
To connect Coinbase to JetScalp, create an API key on the Coinbase Developer Platform (CDP) and enter it in the connection settings.
A CDP key has two parts:
- Key name — the API key identifier: for an ECDSA key, in the form
organizations/{org_id}/apiKeys/{key_id}; for an Ed25519 key, itsidfrom the key’s JSON file. - Private key — the secret key used to sign requests: for an ECDSA key, in the format
-----BEGIN EC PRIVATE KEY----- … -----END EC PRIVATE KEY-----; for an Ed25519 key, a Base64 string.
JetScalp works with Coinbase through the Advanced Trade API — spot trading. Coinbase futures and perpetual contracts are not supported in JetScalp.
JetScalp needs a Secret API Key. A key with either CDP portal signature algorithm works — ECDSA or Ed25519.
Official guide: API Key Authentication .
1.Open API key management
Sign in with your Coinbase account on the CDP portal’s secret keys page — the API Keys → Secret API Keys tab.
2.Create an API key
Click Create API key and enter a key name (API key nickname), for example JetScalp. Then expand the API restrictions and Advanced Settings sections — they contain the permissions, IP addresses and signature algorithm.
3.Configure permissions
JetScalp needs access to viewing accounts, orders and fills (View) and to placing and canceling orders (Trade):
- View
- Trade
- Transfer
Important: JetScalp does not need the funds transfer permission (Transfer) — do not enable it. A key with this permission can move funds out of your account.
If your account has several portfolios, select the one you will trade in: JetScalp works with the balance and orders of the portfolio the key is bound to.
4.Restrict access by IP
In the API restrictions section, add the IP address JetScalp connects to Coinbase from to the allowed IP list (IP allowlist). If JetScalp works through a proxy, enter the IP address Coinbase sees when you connect through that proxy.
If you do not know which IP to enter, find it out first: with a wrong IP, Coinbase rejects the connection.
5.Choose the signature algorithm and create the key
The Advanced Settings section sets the Signature algorithm. The portal offers Ed25519 by default; you can keep it or choose ECDSA — JetScalp works with both.
Click Create API key and, if Coinbase asks, enter the two-factor authentication code. The key window shows the key name (API key name) and the private key (Private key).
6.Save the key
Save the key immediately after creation. The easiest way is to click Download API key — a JSON file with the key name and the private key is downloaded.
Important: The private key cannot be retrieved again. If it is lost, delete the key and create a new one.
7.Add the connection in JetScalp
Open Settings → Connections, click Add connection below the connection list and click the tile Coinbase. The connection appears in the list, and its settings appear on the right.
Fill in the connection settings:
| Field | Value |
|---|---|
| Name | The connection name in the list. By default it is the exchange or broker name; you can change it. |
| Key name | The key name from Coinbase: for an ECDSA key, in the form organizations/…/apiKeys/…; for Ed25519, the key's id |
| Private key | The private key from Coinbase. |
| Proxy | A proxy from the list or None. See Proxy settings. |
An ECDSA private key spans several lines, while the Private key field is a single line, so it is easier to load the key from a file: click … to the right of the field and select the JSON file downloaded in the CDP portal (or a .pem file with the key). JetScalp fills in the Private key field and, from a JSON file, the Key name field as well (from name for an ECDSA key, from id for Ed25519).
If you do not have the file, paste the privateKey value exactly as it is written in the JSON. An Ed25519 key is a single Base64 line; paste an ECDSA key as one line, with line breaks written as \n:
-----BEGIN EC PRIVATE KEY-----\nMHcCAQEE…\n-----END EC PRIVATE KEY-----\n8.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:
- Coinbase is connected.
- The account balance is shown.
- Open orders are shown.
- Orders are placed and canceled.
When connecting, JetScalp checks that the key has the View and Trade permissions; if either is missing, the connection is not established.
JetScalp places market and limit orders on Coinbase. A position stop loss is placed on the exchange as a stop-limit order with a limit price 5% worse than the stop level (Coinbase has no market stop orders), and a take profit as a limit order. If Coinbase rejects the take profit because the funds are already held by the stop loss, the terminal executes the take profit itself. Regular stop orders are also executed by the terminal.
If the connection does not work
Invalid key name or private key
Check that the key name is copied completely and the private key in full: for an ECDSA key, with the -----BEGIN EC PRIVATE KEY----- and -----END EC PRIVATE KEY----- lines; for Ed25519, the whole Base64 string. The most reliable way is to load the key from the downloaded JSON file with the … button.
If the private key cannot be read, the connection is not established and JetScalp shows “Coinbase: could not parse the API key — …”: the text after the dash says what is wrong with the key (for example, “private key is neither PEM nor Base64”).
Insufficient permissions
If the connection is rejected with a message about key permissions, check that the key has View and Trade enabled.
Wrong portfolio
If the balance or orders are not what you expect, check which portfolio the key is bound to. To trade in another portfolio, create a key bound to it.
IP restriction
If the key has an IP restriction, make sure the IP address of the computer or proxy is in the allowed list.
Wrong time on the computer
Every request to Coinbase is signed with a token that is valid for 2 minutes. JetScalp syncs its time with the exchange clock, but if signature errors keep occurring, make sure automatic time synchronization is enabled on your computer.
API key deleted
Open Coinbase Developer Platform → API Keys → Secret API Keys and make sure the key exists. Delete a compromised key and create a new one.
Security
Never share your API key name and private key, or the downloaded key JSON file — 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 Coinbase Developer Platform right away and create a new one.
Once the key is entered in JetScalp, keep the downloaded JSON file in a safe place or delete it.