View as markdown
Endpoints · Signals

Delete a custom signal

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

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. Write access requires Scale or above; Hobby/Pro return `403 custom_signals_tier_required`.

Plan access

Scale and above. Hobby/Pro can read the catalog but writes return 403 custom_signals_tier_required.

Rate limit

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

Capacity

Unlimited custom signals per account on Scale and Enterprise.

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 }.
403
custom_signals_tier_required — Hobby/Pro can read but not write custom signals.
404
not_found — no custom signal with that name on this account.
409
signal_referenced with referencing_signals array. Pass ?force=true to bypass.