View as markdown
Endpoints · Signals

Delete a custom signal

DELETEhttps://api.tickerbot.io/v2/signals/{signal}

By default, DELETE is cascade-safe: it refuses with 409 signal_referenced if any of your other custom signals reference this signal by name. The response carries a referencing_signals array so you can audit before deciding.

Pass ?force=true to delete anyway. Existing references will compile to unknown_column errors next time the consumer recompiles, so use force when you've already fixed the references.

Body parameters

stringrequired

Custom signal slug (the signal name).

booleandefault false

When true, skip the reference check and delete. References will break on next recompile.

Status codes

200
{ as_of, ok: true }.
404
not_found — no custom signal with that name on this account.
409
signal_referenced with referencing_signals array. Pass ?force=true to bypass.

Notes

  • The reference check is a regex match on the JSONB text of other custom signals' expr_text — false positives are possible (e.g. the name appears in a comment or string literal). False positives are tolerable for a safety warning; tighter detection via compiled-AST walks is a future enhancement.