Endpoints · Signals

Delete a custom signal

DELETE/v2/signals/{name}

By default, DELETE is cascade-safe: it refuses with 409 `signal_referenced` if any of your strategies (or other custom signals) reference this signal by name. The response carries `referencing_strategies` and `referencing_signals` arrays 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.

Plan access

Included on every plan, Hobby through Enterprise.

Rate limit

Hobby 60/min · Pro 2,000/min · Scale 10,000/min.

Universe

All ~12,000 tracked tickers on every plan.

Body parameters

stringrequired

Custom signal slug.

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_strategies and referencing_signals arrays. Pass ?force=true to bypass.