Custom signals
A custom signal is one you define: a named true/false SQL expression over other signals. Once created, you screen on it by name like a built-in.
Endpoints
| Method | Path | MCP tool | Summary |
|---|---|---|---|
| POST | /v2/signals | tickerbot_create_custom_signal | Saves a named boolean SQL expression you can screen on like a built-in signal. |
| PATCH | /v2/signals/{signal} | tickerbot_update_custom_signal | Edits one of your custom signals: its expression, description or name. |
| DELETE | /v2/signals/{signal} | tickerbot_delete_custom_signal | Deletes a custom signal, unless another of your signals references it. |
Where you can use one
| Surface | Works? | How |
|---|---|---|
Scan q (POST /v2/scan) | Yes | Name it in the WHERE clause; it expands to its SQL at request time. |
Scan aggregate select / group_by / having | Yes | Inside expressions. |
Scan select | Yes | Returns its value (true/false) under its name. |
order | Yes | Sorts by its value (true first with dir=desc) on Run a scan, Get a signal, Subscribe to a scan, Subscribe to a signal and Update a webhook. A scan row carries its value under its name. |
GET /v2/signals/{signal} | Yes | Pass its name as the signal, like a built-in boolean. |
History select (GET /v2/tickers/{ticker}/history) | Yes | Computed per result like a built-in boolean. |
Events with join=state | Yes | Inlined like a built-in signal. |
Events q without join=state | No | It reads the event’s own fields (id, ticker, ts, kind and the payload); add join=state to use a custom signal. |
Events kind=signal | Yes | Its flips are read like a built-in’s, computed when you ask. |
| Subscribe triggers (scan, ticker, signal) | Yes | Expanded and frozen into the webhook at creation; later edits don’t change it. |
The catalog (GET /v2/signals?kind=custom) | Yes | Listed alongside the built-ins, with its expr. |
Nesting
A custom signal’s expression may reference your other custom signals by name, up to five levels deep. A deeper chain or a circular reference is 400 compile_failed (sub-error forbidden_syntax); a signal can’t reference itself, and its name can’t be a built-in’s (409 name_collision).