---
title: "Delete Blacklist API (delete-blacklist)"
description: "Remove a previously blocked phone number from your blacklist. One number per request, not idempotent."
slug: /en/docs/api/delete-blacklist
locale: en
audience: developer
last_updated: 2026-04-29
endpoint:
  method: POST
  path: /v1/delete-blacklist/json
  base_url: https://api.iletimerkezi.com
auth: api-key-and-hash
related: [get-blacklist, add-blacklist, authentication, error-codes]
alternates:
  tr: https://www.iletimerkezi.com/docs/api/delete-blacklist
  en: https://www.iletimerkezi.com/en/docs/api/delete-blacklist
  toplusmsapi: https://toplusmsapi.com/numara-engelle/cikar/json
  a2psmsapi: https://a2psmsapi.com/en/numara-engelle/cikar/json
---

# Delete Blacklist API (delete-blacklist)

The `delete-blacklist` endpoint removes a phone number from your account's blacklist. After removal, `send-sms` can deliver to that number again. One number per request; **not idempotent** — removing a number that is not on the list returns an error.

## Prerequisite: enable API access in the panel

> Before calling this endpoint, the **Allow API access** toggle must be on in your iletiMerkezi panel.
>
> Location: `panel.iletimerkezi.com` → **Settings → Security → Access Permissions**
>
> If it is off, every request returns `401 — Üyelik bilgileri hatalı` ("Authentication failed"). See [authentication.md](./authentication.md).

## Endpoint

| Field | Value |
|---|---|
| Method | `POST` |
| URL | `https://api.iletimerkezi.com/v1/delete-blacklist/json` |
| Content-Type | `application/json` |
| Auth | API Key + Hash (`request.authentication`) |

## Request

### Schema

```
request
├─ authentication
│  ├─ key (string, required)
│  └─ hash (string, required)
└─ blacklist
   └─ number (string, required) — one number, 905XXXXXXXXX / +905XXXXXXXXX / 5XXXXXXXXX
```

### Full example

```json
{
  "request": {
    "authentication": {
      "key": "API_KEY",
      "hash": "API_HASH"
    },
    "blacklist": {
      "number": "905XXXXXXXXX"
    }
  }
}
```

## Response

### Success (200)

```json
{
  "response": {
    "status": {
      "code": 200,
      "message": "İşlem başarılı"
    }
  }
}
```

`İşlem başarılı` means "Request successful" in Turkish. The number has been removed from the blacklist.

### Error responses

#### 401 — Üyelik bilgileri hatalı ("Authentication failed")

See [authentication.md](./authentication.md).

#### 466 — Hatalı numara ("Invalid number")

The number does not match a Turkish carrier prefix (50 / 53 / 54 / 55, etc.).

#### 474 — Bu numara üzerindeki engelleme kaldırılamaz ("Cannot remove block on this number")

The number is not on your blacklist (or removal failed). Verify presence with [`get-blacklist`](./get-blacklist.md) before calling.

#### Other error codes

For `400, 404`: see [error-codes.md](./error-codes.md).

## Code samples

### cURL

```bash
curl -X POST 'https://api.iletimerkezi.com/v1/delete-blacklist/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "request": {
      "authentication": {
        "key": "'"$ILETIMERKEZI_API_KEY"'",
        "hash": "'"$ILETIMERKEZI_API_HASH"'"
      },
      "blacklist": { "number": "905XXXXXXXXX" }
    }
  }'
```


## Common pitfalls

- **Not idempotent.** Unlike `add-blacklist`, removing a number that is not on the list returns `474 — Cannot remove block on this number`. Wrap the call in error handling, or pre-check with [`get-blacklist`](./get-blacklist.md).
- **One number per request.** `blacklist.number` is a string, not an array. Loop for bulk removals.
- **466 vs 474.** `466` is a number-format error (bad prefix); `474` means the format is fine but the number isn't on the list. Handle them separately in your error flow.
- **Number format flexible.** `905...`, `+905...`, and `5...` are all accepted; the backend matches the stored entry regardless of input format.

## Related

- [Get blacklist](./get-blacklist.md)
- [Add to blacklist (add-blacklist)](./add-blacklist.md)
- [Authentication](./authentication.md)
- [Error code table](./error-codes.md)