Receive a TradingView alert

POST

https://hooks.liftx.io

tradingview

events

Receive a restricted-capability TradingView webhook

curl --request POST \
  --url https://hooks.liftx.io/v1/tradingview/events \
  --header 'Content-Type: application/json' \
  --data '
{
  "token": "<string>",
  "command": {
    "client_command_id": "<string>",
    "issued_at": 123,
    "expires_at": 123,
    "exchange_link_id": 4503599627370496,
    "instrument_id": "<string>",
    "source_instance_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "sequence": 2,
    "binding_revision": 2,
    "expected_revision": 2,
    "client_position_id": "<string>",
    "position_started_at": 2
  }
}
'

import requests

url = "https://hooks.liftx.io/v1/tradingview/events"

payload = {
    "token": "<string>",
    "command": {
        "client_command_id": "<string>",
        "issued_at": 123,
        "expires_at": 123,
        "exchange_link_id": 4503599627370496,
        "instrument_id": "<string>",
        "source_instance_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
        "sequence": 2,
        "binding_revision": 2,
        "expected_revision": 2,
        "client_position_id": "<string>",
        "position_started_at": 2
    }
}
headers = {"Content-Type": "application/json"}

response = requests.post(url, json=payload, headers=headers)

print(response.text)

const options = {
  method: 'POST',
  headers: {'Content-Type': 'application/json'},
  body: JSON.stringify({
    token: '<string>',
    command: {
      client_command_id: '<string>',
      issued_at: 123,
      expires_at: 123,
      exchange_link_id: 4503599627370496,
      instrument_id: '<string>',
      source_instance_id: '3c90c3cc-0d44-4b50-8888-8dd25736052a',
      sequence: 2,
      binding_revision: 2,
      expected_revision: 2,
      client_position_id: '<string>',
      position_started_at: 2
    }
  })
};

fetch('https://hooks.liftx.io/v1/tradingview/events', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

{
  "id": "22222222-2222-4222-8222-222222222222",
  "client_command_id": "alert:55555555-5555-4555-8555-555555555555:1893456000:open",
  "action": "open",
  "state": "accepted",
  "position_id": "11111111-1111-4111-8111-111111111111",
  "error_code": null,
  "created_at": 1893456000,
  "updated_at": 1893456000
}

Preview contract. Production availability remains subject to activation and release qualification. Examples are synthetic; the documentation cannot submit requests.

Authorization

Restricted TradingView key in body token; ordinary API keys are invalid.

Behavior

Use the hooks host, valid JSON and exactly one nonnull alert or command. No client-certificate setup is required. New durable acceptance returns 202; identical retry returns 200; temporary or inactive admission returns 503. The application admission budget is two seconds. Receipts are not execution feedback to Pine.

JSON body example

The following shows the request shape, not live credentials or executable market defaults. Replace timestamps only when creating a new reviewed intent; never mutate them on a command retry.

{
  "token": "YOUR_RESTRICTED_TRADINGVIEW_KEY",
  "alert": {
    "fired_at": "{{timenow}}",
    "max_lag_seconds": 60,
    "action": "open",
    "target": "position",
    "exchange_link_id": 17,
    "instrument_id": "COPY_EXACT_CATALOG_ID",
    "source_instance_id": "55555555-5555-4555-8555-555555555555",
    "binding_revision": 1
  }
}

Send to https://hooks.liftx.io/v1/tradingview/events, not the API host. This example assumes a guided setup that already stores the OPEN request. TradingView substitutes {{timenow}}; a direct sender must supply the canonical UTC timestamp itself.

Response and errors

The generated response schema below is the wire contract. Preserve fixed-point strings, nullable fields and endpoint-specific envelopes. Inspect HTTP status and Content-Type before decoding failures; reused trading routes may return JSON or plain text. Authentication, entitlement and exact link/instrument restrictions apply in addition to endpoint validation. See errors and recovery. Do not automatically repeat a mutation after transport ambiguity. Trading commands reuse the exact immutable identity; credential issuance and template writes require their documented metadata/read reconciliation. Read the related guide for lifecycle, units and recovery semantics.

Body

application/json

Option 1
Option 2

Exactly one non-null command or alert object. The restricted body token authenticates either transport; both converge on the same canonical command admission.

token

string

required

write-only

command

object

required

Immutable source/revision and exact market. Each new OPEN uses a new lifecycle reference and sequence above the source watermark. Known-position termination remains per-reference ordered; groups freeze at most 64 targets and never reselect on retry. Advanced OPEN and MODIFY use the existing PositionRequest; capped MODIFY preserves OPEN rows. Pine has no execution-feedback channel.

Show child attributes

alert

object

Ordinary OPEN/EXIT alert pair. Guided OPEN omits request; advanced OPEN requires full canonical request. OPEN identity/reference are derived from source and fired second. Sequence is Unix milliseconds with termination ranked +1. One distinct OPEN and EXIT per second per setup; identical payload duplicates return original receipt, changed payload conflicts. EXIT has no exact lifecycle reference. Source authority, permissions, quantity cap, receipt and trading execution remain canonical. Do not mix this pair with a Pine producer.

Show child attributes

Response

Identical accepted event

Durable command receipt, never a fill/completion assertion. Terminal request fields correlate a durable termination owner handoff. Terminal arm writes kind/sequence while retaining dispatching; owner return or startup canonical evidence advances handed_off. Group parent position_id is null. Precedence is operator_required, dispatching, accepted, then homogeneous resolved state or partial. Zero-target parent is execution_observed. Counts and child states do not prove exposure is flat.

string<uuid>

required

client_command_id

string

required

action

string

required

state

enum<string>

required

Available options:

accepted,

dispatching,

handed_off,

execution_observed,

rejected,

expired,

operator_required,

partial

position_id

string<uuid> | null

required

error_code

string | null

required

created_at

integer<int64>

required

updated_at

integer<int64>

required

terminal_request_kind

enum<integer>

Available options:

1,

2

terminal_request_seq

integer<int64>

Required range: x >= 1

group_id

string<uuid>

Parent group on a child termination receipt.

group

object

Counts sum to the immutable target_count. Zero targets records an observed empty selection, not market flatness.

Show child attributes

targets

object[]

Group detail only: at most 64 frozen ordinary termination receipts. Targets cannot contain nested groups or target arrays. Omitted on list responses and zero-target groups.

Maximum array length: 64

Show child attributes

Receive a restricted-capability TradingView webhook

curl --request POST \
  --url https://hooks.liftx.io/v1/tradingview/events \
  --header 'Content-Type: application/json' \
  --data '
{
  "token": "<string>",
  "command": {
    "client_command_id": "<string>",
    "issued_at": 123,
    "expires_at": 123,
    "exchange_link_id": 4503599627370496,
    "instrument_id": "<string>",
    "source_instance_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "sequence": 2,
    "binding_revision": 2,
    "expected_revision": 2,
    "client_position_id": "<string>",
    "position_started_at": 2
  }
}
'

import requests

url = "https://hooks.liftx.io/v1/tradingview/events"

payload = {
    "token": "<string>",
    "command": {
        "client_command_id": "<string>",
        "issued_at": 123,
        "expires_at": 123,
        "exchange_link_id": 4503599627370496,
        "instrument_id": "<string>",
        "source_instance_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
        "sequence": 2,
        "binding_revision": 2,
        "expected_revision": 2,
        "client_position_id": "<string>",
        "position_started_at": 2
    }
}
headers = {"Content-Type": "application/json"}

response = requests.post(url, json=payload, headers=headers)

print(response.text)

const options = {
  method: 'POST',
  headers: {'Content-Type': 'application/json'},
  body: JSON.stringify({
    token: '<string>',
    command: {
      client_command_id: '<string>',
      issued_at: 123,
      expires_at: 123,
      exchange_link_id: 4503599627370496,
      instrument_id: '<string>',
      source_instance_id: '3c90c3cc-0d44-4b50-8888-8dd25736052a',
      sequence: 2,
      binding_revision: 2,
      expected_revision: 2,
      client_position_id: '<string>',
      position_started_at: 2
    }
  })
};

fetch('https://hooks.liftx.io/v1/tradingview/events', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

{
  "id": "22222222-2222-4222-8222-222222222222",
  "client_command_id": "alert:55555555-5555-4555-8555-555555555555:1893456000:open",
  "action": "open",
  "state": "accepted",
  "position_id": "11111111-1111-4111-8111-111111111111",
  "error_code": null,
  "created_at": 1893456000,
  "updated_at": 1893456000
}

Discovery and account data

Positions and history

Templates

Commands and streams

TradingView webhook

Session-only Settings

Receive a TradingView alert

Authorization

Behavior

JSON body example

Response and errors

Body

Response

​Authorization

​Behavior

​JSON body example

​Response and errors

Body

Response

Authorization

Behavior

JSON body example

Response and errors