curl -X PATCH "https://api.telzino.com/v1/accounts/7f1e2d3c-…/suppression-settings" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "wide_suppression_enabled": true }'
curl -X PATCH "https://api.telzino.com/v1/resellers/5c4b3a29-…/suppression-settings" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "wide_suppression_enabled": true }'
curl "https://api.telzino.com/v1/resellers/5c4b3a29-…/suppression-settings" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN"
{ "data": { "wide_suppression_enabled": true } }
{ "data": { "wide_suppression_enabled": false, "enforced_by_partner": true } }
{
"error": "enforced_by_partner",
"error_description": "Partner-wide suppression is on, so this reseller setting is enforced by the partner"
}
Suppression List
Suppression Settings
Turn partner-wide or reseller-wide suppression of mid-call opt-outs on or off
PATCH
/
v1
/
accounts
/
{account_id}
/
suppression-settings
curl -X PATCH "https://api.telzino.com/v1/accounts/7f1e2d3c-…/suppression-settings" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "wide_suppression_enabled": true }'
curl -X PATCH "https://api.telzino.com/v1/resellers/5c4b3a29-…/suppression-settings" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "wide_suppression_enabled": true }'
curl "https://api.telzino.com/v1/resellers/5c4b3a29-…/suppression-settings" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN"
{ "data": { "wide_suppression_enabled": true } }
{ "data": { "wide_suppression_enabled": false, "enforced_by_partner": true } }
{
"error": "enforced_by_partner",
"error_description": "Partner-wide suppression is on, so this reseller setting is enforced by the partner"
}
Two settings decide which list a mid-call opt-out is written to. Both are off by default.
With both off, opt-outs go to the calling organization’s own list. Partner-wide overrides reseller-wide. While it is on, every reseller under the partner reports
| Setting | Endpoint | When on |
|---|---|---|
| Partner-wide | /v1/accounts/{account_id}/suppression-settings | Opt-outs from any agent under the partner go to the partner list |
| Reseller-wide | /v1/resellers/{reseller_id}/suppression-settings | Opt-outs from any agent under the reseller go to the reseller list |
enforced_by_partner: true, and a PATCH to a reseller setting returns 409 enforced_by_partner.
The settings decide only where opt-outs are written. Every call is still checked against the organization, reseller and partner lists. Turning a setting off stops new opt-outs being written there; numbers already on the list stay blocked. Turning one on does not move existing organization entries. Every change is recorded with who made it. See Outbound Compliance.
Both endpoints accept GET (read) and PATCH (change).
Who can use it
| API key | Partner setting | Reseller setting |
|---|---|---|
| Account | Read and change | Read and change, for any reseller in the account |
| Reseller | Read only (PATCH returns 403 forbidden) | Read and change, its own reseller only |
| Organization | No (403 forbidden) | No (403 forbidden) |
Path Parameters
Partner setting. The partner’s account UUID. It must be the account of your API key; any other id returns
404.Request Body (PATCH)
Response
Reseller setting only.
true while partner-wide suppression is on: opt-outs go to the partner list and this setting cannot be changed.A partner-wide opt-out blocks calls to that number from every business under the partner, including unrelated ones. That is why both settings are off by default. Check with counsel before turning one on.
curl -X PATCH "https://api.telzino.com/v1/accounts/7f1e2d3c-…/suppression-settings" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "wide_suppression_enabled": true }'
curl -X PATCH "https://api.telzino.com/v1/resellers/5c4b3a29-…/suppression-settings" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "wide_suppression_enabled": true }'
curl "https://api.telzino.com/v1/resellers/5c4b3a29-…/suppression-settings" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN"
{ "data": { "wide_suppression_enabled": true } }
{ "data": { "wide_suppression_enabled": false, "enforced_by_partner": true } }
{
"error": "enforced_by_partner",
"error_description": "Partner-wide suppression is on, so this reseller setting is enforced by the partner"
}
| Code | Meaning |
|---|---|
200 | The setting (after the change, for PATCH) |
400 | The body is not { "wide_suppression_enabled": true } or false |
403 | The API key cannot read or change this setting |
404 | Account or reseller not found, or access denied |
409 | enforced_by_partner: partner-wide suppression is on, so the reseller setting is locked |