Skip to main content

​
Choose the right access method

An API key and a TradingView key are different credential kinds. Naming an API key “TradingView” does not turn it into a webhook credential. Create each through its own tab in Settings → Integrations.

​
Prepare the account

  1. Confirm that API or webhook execution is available in the environment you intend to use. See availability.
  2. Sign in to Liftx, link the intended exchange account, and confirm whether it is demo or live.
  3. Confirm Pro or trial access. Existing paid-renewal grace follows Liftx subscription policy; it is not a separate integration extension.
  4. Select a catalog instrument supported by that link. A display ticker such as BTCUSDT is not sufficient to identify an account, product, settlement asset, or environment.
  5. Decide the permitted operations and market scope before creating a credential. Use separate credentials for independent strategies.
  6. Keep fresh password or Apple authentication available, and complete MFA if enabled when Liftx requests it.

​
Understand quantities before issuing a command

Liftx uses decimal coefficients and scales: "1250" with scale 2 means 12.50. The quantity_asset identifies the asset used for entered OPEN quantities. Price, base quantity, quote notional, contract count, and margin are different quantities. The TradingView maximum OPEN quantity is evaluated in the instrument’s canonical normalized quantity unit, displayed during setup. For spot and linear contracts this is generally the base asset; for inverse contracts it is the quote face unit. It is not a generic “USDT to spend” cap. A multiple-position setup can create several positions each within its cap; the cap is not aggregate account exposure. Read the full quantity and position contract before using leverage, grids, or quote-denominated input amounts.

​
Validate in stages

1

Prove the read path

With an API credential, read discovery, exact linked-account metadata, and the instrument catalog. Verify that prohibited accounts or instruments remain inaccessible. Keep trading permissions disabled unless the workflow needs them.
2

Prepare the full intent

Use a demo account and a deliberately small, valid amount chosen against its catalog rules. Preserve the complete command body and its identity. For TradingView, copy the generated setup immediately into a private location before leaving the page.
3

Submit one controlled command

Follow the API guide or TradingView setup. Check the HTTP response or TradingView webhook status. Then inspect Liftx Activity and the actual position.
4

Exercise the lifecycle

Verify OPEN, protection behavior, an explicit current-state modification where supported, and termination. Termination can cancel pending orders and close remaining exposure. Verify the final position; do not infer flatness from an accepted exit signal.
5

Verify failure handling

Exercise identical retry, changed-payload conflict, expiry, revocation, independent-strategy isolation, and reconnect recovery. Stop and reconcile any uncertain result before creating new trading intent.

​
Move from an example to a controller

A production integration needs durable local intent storage, stable identities, bounded retries, clock discipline, receipt reconciliation, and an explicit response to uncertainty. Use the API when a decision depends on Liftx’s current state. A Pine script’s local phase and TradingView’s strategy emulator do not provide that state. Examples intentionally avoid automatic compensating trades, automatic reversal, and blind replay of modifications. Those actions need an explicit strategy decision based on current, authoritative evidence.