Prepare your Kraken connection
You need an exchange account with the intended market available, an API key with the permissions required by your orders, and an alert source that can send webhooks. Read this guide without an account; sign in to Flipr.Cloud only when you configure the connection.
Integration scope
This guide concerns linear Futures. Futures credentials differ from Spot credentials. The retired public Futures Demo and its replacement are not available through the current Flipr.Cloud Testnet path. See Exchange Quirks for the reviewed capabilities and limits. The available choices in API Keys determine what can be connected.
1. Create the Kraken API key
Create the credentials inside Kraken Derivatives. Its API keys are separate from Spot keys, so an existing Kraken Spot connection does not supply the credentials for this Futures guide.
Open the account menu, choose Settings, then Create Key in the API panel. Set General API to Full Access for order execution and Withdrawal API to No Access. A General API key set to Read Only can read account information but cannot place orders.
Copy the Public key into Flipr.Cloud’s API Key field and the Private key into API Secret. Kraken shows the private key only once. Select the Futures market in Flipr.Cloud and use the live connection described in Exchange Quirks.
See Kraken’s Derivatives API key instructions for the current settings and permission definitions.
2. Save the connection in Flipr.Cloud
Open API Keys, select the exchange and supported market, enter the requested credentials, and choose a clear label such as My_API_Key. The header uses this exact saved label. A name ending in _F or _S does not select a market: that is part of the saved connection configuration.
Use the connection test and inspect its result. Copy the webhook URL from the saved key or Webhook Configuration. Use the displayed regional URL and whitelist instead of a hostname copied from an old tutorial.
3. Configure the TradingView alert
Enable webhook delivery in your alert, paste the copied URL and write the Smart Syntax message. Verify the symbol supported by your selected market and replace My_API_Key with your saved label. Keep the URL private. Read the Syntax Reference for headers, quantities and multiple blocks.
BTCUSDT on My_API_Key
balance4. Verify the complete path
Start with a balance request. Check the alert delivery result and Flipr.Cloud’s Execution History. A successful balance request verifies that path; it does not certify order types, sizing or protection handling.
Before sending a trading signal, review Exchange Settings, market sizing and SL/TP handling. Signal Factory sends to the selected account; it is not a built-in simulator. In a supported test environment, inspect actual fills, remaining orders and position state on the exchange.
Resolve connection and order errors
Check credentials, environment, permissions, whitelist, available funds, symbol and minimum size. Use the exchange error returned by the execution and the troubleshooting guide. A timeout does not prove that no order was submitted: inspect the result and exchange state before retrying.