View as markdown
Endpoints · Signals

All signals

GEThttps://api.tickerbot.io/v2/signals

Every signal you can name in a query — the built-in schema columns and your own custom signals, in one catalog.

enum

Filter by kind (custom accepted as a legacy alias for expression). Omit to return both.

builtinA built-in column on the live schema.
expressionOne of your own custom signals. (custom is accepted as a legacy alias.)
integerdefault 50

Page size for the custom-signal slice. Max 200.

string

Opaque cursor from a prior response.

as_ofstring

Server time this response was assembled (ISO 8601).

countnumber

Rows in this page — the canonical count, equal to `count_builtin` + `count_custom`.

count_builtinnumber

Built-in columns in the catalog.

count_customnumber

Your custom signals.

next_cursorstring

Opaque token for the next page; `null` on the last page. Pass it back as `cursor`.

signalsarray

The catalog, your custom signals first, then built-ins. Built-ins carry `kind: builtin`; yours carry `kind: expression` with the `expr`.

200
Success — the response shape is documented under Returns above.
400
bad_request — invalid kind value or malformed cursor.
  • Built-ins are tagged kind: 'builtin' and carry name, type, source; your own are tagged kind: 'expression' and carry name, description, expr, created_at, updated_at.
  • Pagination applies only to the custom-signal slice. Built-ins are a small fixed set and come back in their entirety on every page.
  • Built-in rows are enriched from the live signal spec: description, category, cadence, ticker_scope, history, history_since, resolutions, asset_classes, asof (whether the column is historized, i.e. readable via ?asof=), plus flag_kind/firing on booleans and unit where defined. If the spec is briefly unreachable the catalog degrades to bare name + type + source rows rather than erroring.
  • Custom signals are private and keyed on (user_id, name). Different users may use the same name for different signals.