Live matches
https://api.tickerbot.io/ v2/ signals/ {signal}Return the set of tickers where the named signal is true (for boolean flags) or where the numeric value satisfies a single-bounded condition. Sorted by signal value descending for numerics, alphabetically by ticker for booleans. Pass asof — a date for the match set at the close of that day, or a full ISO timestamp for the match set at that intraday moment (_meta.resolution reports the granularity served).
Query parameters
stringrequiredA column on `ticker`. Boolean flags (e.g. `golden_cross`, `above_sma_50`) are detected automatically; numerics (e.g. `rsi_14`, `market_cap`, `pe_ratio`) require a condition.
stringRequired for numeric signals. Single bound, format `<op><value>`. Operators: `>`, `>=`, `=`, `!=`, `<`, `<=`. Examples: `>70`, `<=200`, `!=0`. Ignored for boolean flags.
stringOptional. A `YYYY-MM-DD` date matches at the close of that day; a full ISO timestamp matches at that intraday moment. Plan window: Free reaches back 30 days; every paid plan is unlimited (`403 asof_tier_required` beyond the window).
stringOptional. Scope to a system or caller-owned universe slug.
integerdefault 50Page size. Max 200.
stringOpaque cursor from the previous response.
Status codes
200as_of, count, next_cursor, and results. When asof is set, response carries _meta.resolution (the granularity served: minute, hourly, or daily) and _meta.frozen_fields for static columns.400condition, malformed condition, malformed asof, or invalid cursor.404Notes
- Custom signals:
{signal}may be one of your custom signals — it resolves as a boolean signal (matches where its predicate is true;conditionis ignored). See Create a custom signal. - For boolean flags, the response value is
true/false. For numerics it's the column value at the time of the request. - Pair with
asofto ask "who matched at a past moment" — see [As-of matches](/docs/endpoints/signals/asof). For a per-ticker time series of one signal, see [Signal history](/docs/endpoints/signals/history).