longbridge__developers/openapi.yaml at docs/signals-api

mirror of https://github.com/longbridge/developers.git synced 2026-09-19 03:34:09 +08:00

Files

T

Jason Lee 1a637e7d0b docs: Align the signals reference with the RPC contract

Checked the reference against the `QuerySignals` / `Signal` RPC definitions
and against production responses:

- `status` documents its lifecycle values (0 pending … 5 analysis submit
  failed) instead of being left unexplained.
- `total` is `int32`, matching `QuerySignalsResponse`.
- `risk_level` and `display_control` are dropped from the field tables and
  examples — neither is in the `Signal` message, and production returns
  neither.
- `catalyst_name` says what it matches: the triggering factor's name
  (`EARNINGS_RELEASED`, `macd_12_26_9`), not the prose `key_catalyst` a signal
  displays. Filtering by the value shown in `key_catalyst` returns nothing, so
  both fields now spell out which is which.
- `start_time` / `end_time` also accept a Unix timestamp (≥ 10¹² read as
  milliseconds), per the field definitions.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-25 20:19:31 +08:00

138 KiB Raw Permalink Blame History

138 KiB

Raw Permalink Blame History