Prepare your OKX 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
Provide the API key, secret and passphrase. Select Spot or Futures to match your account; use a separate OKX Demo Trading API key for simulated mode. See Exchange Quirks for the reviewed capabilities and limits. The available choices in API Keys determine what can be connected.
1. Create the OKX API key
In your exchange’s API management, create credentials for the intended account and environment. Grant the read and trading permissions required for your workflow; do not enable withdrawals for this connection. Copy the applicable IP whitelist shown in Flipr.Cloud’s API Keys page to the exchange’s restrictions.
Keep secret credentials private. Live, Demo and Testnet keys are not interchangeable. If a simulated environment is not integrated, selecting a legacy Testnet option does not make live orders simulated.
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.