Deprecated — lifting a suppression now requires the dashboard
⚠️ Always refuses. Lifting a suppression is a deliberate, reasoned act: it now requires a dashboard session and a written justification (POST /v1/dnc/{id}/remove, session-only), and is recorded in the audit trail. API keys can ADD suppressions — an opt-out must land within seconds — but can no longer silently make an opted-out number callable again.
Requires the write scope. A key with less gets 403 insufficient_scope.
Deprecated
Authorization: Bearer tone_live_… or tone_test_…. The prefix IS the environment: a test key reaches only the sandbox, and no request field bridges the two.
In: header
Path Parameters
The suppression entry's id.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/v1/dnc/string"{ "data": null}Numbers on the Do-Not-Call list
Your own suppression list — the only list the gate hard-blocks on. Search accepts whatever someone types: +91 98765 43210, 09876543210 and 4321 all work.
One sealed evidence record
The full evidence document plus its seal: the content hash, the previous record’s hash, and the chain position. Recompute sha256 over the canonical content to prove the document was not altered; walk the verify endpoint to prove the whole chain.