campaign_dnc_override_enabled
- HTTP status
- 409
- Retry
- No
- Execution
- Nothing was done
- Admin needed
- Yes
Campaign calls numbers on the do-not-call list. A campaign's do-not-call screening can be switched off only in the console, by a person (the campaign's dnc_screening is then disabled_in_console). The API never starts or resumes such a campaign, so no API key can place calls to numbers on the do-not-call list. Nothing was dialled.
What it means
The API returns HTTP 409 with error.code set to campaign_dnc_override_enabled. The default message is: "This campaign is set in the console to also call contacts on the do-not-call list, so it cannot be started or resumed through the API."
Common causes
- The campaign's console setting "also call contacts on the Do-Not-Call list" is on.
How to identify it
Check the response status (409) and error.code (campaign_dnc_override_enabled). Branch on error.code, not on the message text: messages can be reworded, codes do not change within v1. Log error.request_id (also sent as the X-Request-Id header) so support can find the request.
What to do
- Ask a workspace admin to switch the setting off in the console, then start or resume it through the API.
- Or start it from the console, where that decision is made.
Retry guidance
Do not resend the request, and do not change settings, to get around this refusal. A new request is appropriate only when the rule genuinely no longer applies: the person asked to be called or gave consent, or the permitted calling window has started.
Did anything happen?
This request was refused before any call was placed and before anything was charged.
Idempotency
No call was placed. If you sent an Idempotency-Key, the refusal is not stored under it. If the rule later stops applying (for example the person gives consent), place a new call (with a new key, if you use one).
Who can fix it
Nobody should change data to make this call go through. Remove a do-not-call entry or record consent only when the person asked you to, and keep a record of who asked and when; these changes are audited. See Consent and DNC.
When to contact support
If the error persists after the steps above, contact support@relationsai.com. See Support for what to include (the request_id, the time in UTC, the operation, and whether you used a test or live key) and what never to send (API keys, Authorization headers, webhook signing secrets, recording links, transcripts or customer data).
Example error response
JSON
Operations that can return this error
POST /campaigns/{campaign_id}/start: Start a campaignPOST /campaigns/{campaign_id}/resume: Resume a campaign
See all codes in the error-code reference.