> ## Documentation Index
> Fetch the complete documentation index at: https://docs.liftx.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Choose your integration

> Select API or TradingView access and validate the complete command-to-position workflow.

## Choose the right access method

| Requirement | Use | Reason |
| - | - | - |
| Read balances, current positions, orders, or history | API key | Supports authenticated reads and scoped streams. |
| Open a configured position when a chart condition fires | TradingView JSON alerts | Liftx generates an OPEN message and an optional strategy exit message. |
| Repeat OPEN and EXIT cycles using custom signals | Pine alerts | Pine maintains explicit lifecycle references and monotonic signal identities. |
| Modify the current configuration after fills or manual changes | API controller | Read the current position publication, revision, and order identities, then construct the complete intended request. |
| Terminate all positions owned by one TradingView strategy | TradingView strategy target | Captures eligible positions from that setup on its exact market. |
| Terminate manual positions and other strategies on one market | TradingView market target with explicit grant | Broader authority requires a separate setup permission. |
| Trade through ChatGPT or Claude | Not available yet | MCP remains planned. |

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](https://app.liftx.io/settings/integrations).

## Prepare the account

1. Confirm that API or webhook execution is available in the environment you intend to use. See [availability](/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](/api/position-request) before using leverage, grids, or quote-denominated input amounts.

## Validate in stages

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Submit one controlled command">
    Follow the [API guide](/api/overview) or [TradingView setup](/integrations/tradingview/setup). Check the HTTP response or TradingView webhook status. Then inspect Liftx Activity and the actual position.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.