Guides, manuals and platform references.
Connect a Kraken Futures API key to AlgoWay, create a TradingView webhook route, and send a valid JSON alert to automate orders in your Kraken Futures account. The signal begins in TradingView, AlgoWay receives it at your private webhook URL, and Kraken handles order execution via your own exchange API credentials.
TradingView alert -> AlgoWay webhook -> Kraken Futures account
This is an automated order-routing setup, not a manual TradingView broker connection. The instructions below follow the Kraken API workflow shown in the existing AlgoWay setup manual.
Prepare an active Kraken account with access to Futures trading, an AlgoWay account, and a TradingView indicator or strategy capable of generating alerts. You will also need access to the exchange API settings to create a trading key. Protect API secrets and do not enable withdrawal permissions.
103.241.67.174; always use the value displayed by your own connection.
Why the Futures key matters: Kraken has separate API credential types. Using the Spot key in a Futures route will prevent the intended connection from working. A trading key does not need withdrawal permission.
These keys stay associated with your Kraken route in AlgoWay. You do not put the keys into TradingView alert messages.
In the TradingView Message field, enter the AlgoWay JSON payload for this route. The example below is for a TradingView strategy alert using strategy placeholders:
{
"platform_name": "kraken",
"ticker": "{{ticker}}",
"order_contracts": "{{strategy.order.contracts}}",
"order_action": "{{strategy.market_position}}",
"price": "{{close}}"
}
{{ticker}} supplies the TradingView chart ticker; {{strategy.order.contracts}} supplies the strategy's configured size; {{strategy.market_position}} supplies the market position direction; and {{close}} supplies the price. These placeholders must be used in a strategy context that actually produces the expected values.
Check that the ticker maps to a valid Kraken Futures contract. TradingView symbol names and exchange contract identifiers can differ. Use symbol mapping in AlgoWay when your connection offers it, and verify the symbol before sending a live order.
Recheck the Public Key and Private Key. Confirm that the key was created for Kraken Futures, not a different API area. Verify the trusted IP restriction against the IP displayed in AlgoWay. A newly created key may also require time to become active.
Open AlgoWay Webhook Logs to determine whether the webhook arrived, whether the JSON was accepted and whether Kraken returned an exchange-side error. Check market permissions, the Futures symbol, order quantity, market status and your account's ability to place trades.
Inspect the TradingView placeholder values, the quantity multiplier in AlgoWay and the connection's trading mode. Different strategies may use buy, sell, long or short differently; confirm the resulting JSON in the logs before running unattended.
Key takeaway: Create the correct Kraken Futures API credentials, save the Kraken connection in AlgoWay, copy its private webhook URL, and use the matching JSON in a TradingView alert. Test both webhook delivery and exchange execution before enabling live automation.
No. The process in this guide uses a Kraken Futures API key from the Futures API section of Kraken account settings.
AlgoWay needs the Public Key and Private Key generated for the Kraken Futures API connection.
No. The Kraken API setup shown here uses General API full access and Withdrawal API no access.
Copy the unique Kraken webhook URL or UUID from the AlgoWay Trade Webhooks dashboard after creating the connection.