Your DaviddTech signals, your exchange accounts

Read how to translate TradingView alerts into Flipr.Cloud messages before connecting an account. Availability of alerts and exported values depends on your strategy and provider access.

Prepare your DaviddTech alert

Use a TradingView indicator or strategy that exposes the alert condition you need. Follow the provider’s instructions for its alert configuration. Verify whether an alert represents an entry, exit or desired position; those meanings require different messages in Flipr.Cloud.

The strategy-to-execution guide explains how TradingView alerts, Flipr.Cloud and your exchange account fit together.

You need a supported exchange connection and webhook delivery from your signal source. Flipr.Cloud trial duration and quotas follow the current plan configuration; see Pricing.

Connect the account and copy its webhook URL

In API Keys, select the intended exchange, market and supported environment, then save the credentials under a clear label. Copy the displayed webhook URL into the TradingView alert. The label in each message must match the saved key. Demo/Testnet needs matching credentials and a supported integration.

Map entry and exit alerts separately

Example entry on a compatible futures market
BTCUSDT on My_API_Key
if posNone continue
market long 0.01 sl off 2% tp off 5%

This opens only when the position check reports flat. It does not check the provider’s indicator or guarantee that the entry and protections succeed together. Inspect each result.

Separate long-exit alert
BTCUSDT on My_API_Key
close long

Closing a position and cancelling pending orders are different actions. Consult Position, conditions and Cancel to match the signal’s meaning. Do not put entry and exit messages together merely to document a future sequence.

Multi-account signals and staged exits

A header can list several saved key labels, separated by commas. Each account has its own balances and order results; the broadcast is not atomic. See headers and blocks.

For several take-profit levels, calculate all requested exit quantities at placement. A final 100%p order is not automatically reserved as whatever will remain later. Common Examples and Advanced Strategies provide reviewed patterns. Smart OCO can clean up tracked orders when position conditions are met; it does not cancel every remaining exit after a partial fill.

Verify before enabling continuing alerts

Execution and timing

Confirm alert direction, quantities, filled position and protection on the exchange. An HTTP timeout does not establish whether an order ran. Avoid duplicate retries without checking state. The wait command delays execution; it is not a condition on price or profit.

Use Quick Start, Exchange Quirks and Troubleshooting for setup and error diagnosis. Flipr.Cloud executes your messages; it does not validate the profitability of a DaviddTech strategy.

One message, more than one saved account

Read-only broadcast example
BTCUSDT on Key_A, Key_B
balance

Multiple-key headers are a general Flipr.Cloud capability. Each key has its own market, funds and results; execution is not atomic. Read Syntax Reference and Advanced Strategies for the detailed workflow.