tickerbot.io

Create a custom signal

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

Saves a named true/false SQL expression you can screen on, select and subscribe to like a built-in boolean.

stringrequired

Slug matching ^[a-z][a-z0-9_]{0,63}$. Must not collide with any built-in signal name, and 15 names are reserved outright: columns, plus the OHLCV aliases of the history read open/high/low/close/volume/vwap/trades and o/h/l/c/v/vw/n (those resolve to bars before custom lookup). This is the signal's API handle: it's what you reference in q and in the CRUD path.

stringrequired

Boolean SQL predicate. May reference built-in signals and other custom signals you own. Must evaluate to true/false. Max 4000 chars. Stricter grammar than scan q: comparisons, AND/OR/NOT, IN, BETWEEN, IS [NOT] NULL, arithmetic and the functions abs/coalesce/round/least/greatest. An expression that scans fine can still be rejected here with compile_failed. What you send is what you read back: responses echo your expression as stored, not its expansion. A signal referencing another custom of yours returns the reference as you typed it; the inlined SQL exists only internally, and is what a subscribe endpoint freezes into a webhook. The one rewrite: a signal named under its pre-2026-09-07 spelling (bollinger_pct_b) is stored under its current name (bollinger_b) and reported in _meta.deprecated_signals.

string

Free-form notes. Max 500 chars. Absent or empty comes back as "" rather than null.

string

Optional unique string (≤255 chars). A retry carrying the same key within 24h replays the original response (Idempotency-Replayed: true header) instead of creating a duplicate; a concurrent duplicate gets 409 idempotency_in_flight; reusing a key for a different request (another method or path, or the same path with a different body) gets 422 idempotency_key_reused. Only a 2xx is stored: after a 4xx or 5xx, a retry with the same key runs again.

as_ofstring

Server time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).

namestring

The slug: the signal's handle in q and in the path.

kindstring

Always custom.

typestring

Always boolean: a custom signal is a yes/no expression.

descriptionstring

Your notes; "" when unset.

exprstring

Your expression as stored (not its expansion).

created_atnumber

Creation timestamp (epoch seconds).

updated_atnumber

Last modification timestamp (epoch seconds).

_metaobject

Only when expr named a signal under its pre-2026-09-07 spelling: deprecated_signals lists each one (requested, use, note). The stored expr carries the current name.

CodeMeaning
201The stored signal at the top level: name, kind: "custom", type: "boolean", description, expr, created_at, updated_at.
400compile_failed (with errors array) when the expression doesn't parse / references unknown signals. bad_request for shape failures. too_many_custom_signals at the 1,000-per-account ceiling (a flat anti-abuse guard, identical for every account); its body carries current and limit so a client can show "N of M used". The ceiling is checked before the request is validated, so at the limit you get this rather than a shape error.
409already_exists (slug taken on this account), name_collision (slug matches a built-in signal) or idempotency_in_flight (a concurrent request with the same Idempotency-Key is still executing).
422idempotency_key_reused: the Idempotency-Key was already used for a different request (another method or path, or the same path with a different body). Use a fresh key per distinct request.
  • Where you can use one, and where you can't: see Custom signals.
  • To vary a numeric threshold per screen, keep the numeric signal raw in q or condition instead of wrapping it in a custom signal.
  • Cross-ticker references (spy.close) work in /v2/scan q only; keep a custom signal single-ticker to use it everywhere.