Endpoints · Signals
All signals
GET
https://api.tickerbot.io/ v2/ signalsEvery signal you can name in a query — the built-in schema columns and your own custom signals, in one catalog.
Query parameters
enumFilter by kind (custom accepted as a legacy alias for expression). Omit to return both.
builtin | A built-in column on the live schema. |
expression | One of your own custom signals. (custom is accepted as a legacy alias.) |
integerdefault 50Page size for the custom-signal slice. Max 200.
stringOpaque cursor from a prior response.
Returns
as_ofstringServer time this response was assembled (ISO 8601).
countnumberRows in this page — the canonical count, equal to `count_builtin` + `count_custom`.
count_builtinnumberBuilt-in columns in the catalog.
count_customnumberYour custom signals.
next_cursorstringOpaque token for the next page; `null` on the last page. Pass it back as `cursor`.
signalsarrayThe catalog, your custom signals first, then built-ins. Built-ins carry `kind: builtin`; yours carry `kind: expression` with the `expr`.
Status codes
200Success — the response shape is documented under Returns above.
400bad_request — invalid kind value or malformed cursor.Notes
- Built-ins are tagged
kind: 'builtin'and carryname,type,source; your own are taggedkind: 'expression'and carryname,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=), plusflag_kind/firingon booleans andunitwhere defined. If the spec is briefly unreachable the catalog degrades to barename+type+sourcerows rather than erroring. - Custom signals are private and keyed on
(user_id, name). Different users may use the same name for different signals.