# dnc_listed

- HTTP status: 422
- Retry: No
- Execution: not started
- Admin needed: no

> **A compliance outcome, not an error to fix:** This refusal protects the person you tried to call. Record it and do not call them now. Never resend the request, remove a do-not-call entry or record consent just to make a call go through. See [Consent and DNC](/guides/consent-and-dnc).

**Number on the do-not-call list.** Every call request is checked against the workspace do-not-call list, and a listed number is refused. The check is always on and matches the number in any format (by its digits, and by its last ten digits when both numbers have at least ten). Campaigns are checked when they start and when they resume: a number added to the list while a campaign is running is not removed from that run, so pause and resume the campaign (the resume is refused while a remaining recipient is listed) or stop it.

## What it means

The API returns HTTP 422 with `error.code` set to `dnc_listed`. The default message is: "This number is on your do-not-call list, so the call was not placed."

## Common causes

- The destination number, or a contact with that number, is on the do-not-call list. The call is refused for compliance.

## How to identify it

Check the response status (`422`) and `error.code` (`dnc_listed`). 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

- Do not call this number, and do not retry: the same request is refused every time.
- Only if the number was added by mistake, or the person has since asked to be called again, a workspace member who manages contacts removes the entry (DELETE /v1/dnc-entries/{dnc_entry_id} with a key holding `dnc:write`, or the Contacts screen in the console). The removal is recorded in the audit log with who made it.

## 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](/guides/consent-and-dnc).

## When to contact support

If the error persists after the steps above, contact [support@relationsai.com](mailto:support@relationsai.com). See [Support](/resources/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
{
  "error": {
    "code": "dnc_listed",
    "message": "This number is on your do-not-call list, so the call was not placed.",
    "details": {},
    "request_id": "req_juciyreuh7sfnlcmrauuzko6",
    "retry": "no",
    "doc_url": "https://docs.relationsai.com/errors/dnc_listed"
  }
}
```

## Operations that can return this error

- [`POST /calls`](/api/calls#place-a-call): Place a call

See all codes in the [error-code reference](/fundamentals/error-codes).