Update a custom signal
https://api.tickerbot.io/ v2/ signals/ {signal}Updates a custom signal you own: its expression, description or name.
Path parameters
stringrequiredCustom signal slug (the signal name). A built-in name answers 404: built-ins are read-only.
Body parameters
stringNew slug: renames the signal and changes its API handle everywhere (same validation as create). Refused while other custom signals reference the current name.
stringNew SQL expression. Re-validated and re-inlined against your other custom signals. Same strict grammar as create: no LIKE/ILIKE, CASE, :: casts or functions beyond abs/coalesce/round/least/greatest. The response echoes your expression as stored, not its expansion (a pre-2026-09-07 signal spelling is stored under its current name and reported in _meta.deprecated_signals).
stringNew description. Not derived from expr, so change both if the prose describes a threshold you are moving.
Returns
as_ofstringServer time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).
namestringThe slug: the signal's handle in q and in the path.
kindstringAlways custom.
typestringAlways boolean: a custom signal is a yes/no expression.
descriptionstringYour notes; "" when unset.
exprstringYour expression as stored (not its expansion).
created_atnumberCreation timestamp (epoch seconds).
updated_atnumberLast modification timestamp (epoch seconds).
_metaobjectOnly 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.
Status codes
| Code | Meaning |
|---|---|
200 | The updated signal at the top level, as create returns it. A request that changes nothing (empty body, or new_name equal to the current name) is also a 200 carrying the signal unchanged, and does not touch updated_at. |
400 | compile_failed on bad expression, bad_request on shape failure or an unknown body key (strict: unknown fields are rejected, not ignored). The accepted keys are description, expr and new_name. |
404 | not_found: no custom signal with that name on this account, or the name is a built-in (rsi_14, 52_week_high), which answers "built-ins are read-only". |
409 | rename_blocked (other custom signals reference the current name, listed in references.signals), name_collision (new name is a built-in signal) or already_exists (you already have a signal with the new name). |
Notes
- Partial update: send
expr,description,new_nameor any combination. - Existing subscriptions keep the old definition: edits and renames reach screens, reads and new subscriptions only. Re-subscribe to apply.