---
title: "Delete blocklists"
method: DELETE
path: "/platform/1/blocklists"
tags: ["platform", "blocklist"]
---

# Delete blocklists

`DELETE /platform/1/blocklists`

## Request

- Base URL: `https://api.infobip.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.infobip.com/platform/1/blocklists`
- Auth: one of:
  - OAuth 2
    - Client credentials
    - Token URL: `https://api.infobip.com/auth/1/oauth2/token`
  - API key in header `Authorization`
  - API key in header `Authorization`
  - HTTP basic

This method allows you to remove someone from blocklist. It accepts delete request and asynchronously deletes all blocklists that match given properties. 

Note: To delete a blocklist, you must list all properties that were defined in the create request. For example, to delete the blocklist with the following properties: 

`{"sender": "10950", "destination": "12022921990", "sourceType": "CUSTOM", "channel": "MMS", "createdDate": "2022-08-18T12:36:42.123Z"}` 

The delete request must contain all present properties, like this: 

`{"blocklist": [{"destinations": [{"to": "12022921990"}], "sender": "10950", "channel": "MMS", "sourceType": "CUSTOM"}`. 

Only when all properties are listed will the blocklist be removed.

## Request body

- 2c1d05f3dc2f46851efe83e0fa7d26e3f8a2e8ee522f9adaaba58b0a33a2be33BlocklistDeleteRequest: Blocklist request.
  - `blocklist` 2c1d05f3dc2f46851efe83e0fa7d26e3f8a2e8ee522f9adaaba58b0a33a2be33BlocklistDelete[], required: Blocklist elements that need to be removed from blocklist. Number of destinations cannot exceed 50 000.
    - `destinations` 2c1d05f3dc2f46851efe83e0fa7d26e3f8a2e8ee522f9adaaba58b0a33a2be33ToDelete[], required: Destination addresses that need to be removed from blocklist.
      - `to` string, required: Destination address that needs to be removed from blocklist. Addresses must be a number in international format (example: `41793026727`), a valid email address (example: `recipient@example.com`) or valid email domain (example: `example.com`).
    - `sender` string: The sender ID that needs to be removed from blocklist. Sender can be alphanumeric or numeric.
    - `channel` 'SMS' | 'EMAIL' | 'VIBER' | 'RCS' | 'MMS' | 'APPLE_MB' | 'WHATSAPP': Channel for which blocklist record/s will be removed.
    - `accountKey` string: Account for which blocklist record/s will be removed. Main account can remove blocklist record/s for their subaccounts. Subaccounts can remove blocklist record/s specific to them. [API to retrieve account key](https://www.infobip.com/docs/api/platform/account-management/get-all-accounts).
    - `sourceType` 'CUSTOM' | 'MO' | 'URL_OPT_OUT' | 'CAMPAIGN': Represents the way blocklist record was created: CUSTOM - blocklist record that was created manually MO - blocklist record automatically created once an end user unsubscribes by replying with a specific keyword (e.g.: STOP). This is applicable for the following channels: SMS, MMS. URL_OPT_OUT - blocklist record automatically created once an end user clicks an opt-out link included in the message. CAMPAIGN - blocklist record automatically created through a triggered event in the Flow (e.g., if the message was not opened in 24h, add to blocklist). If source type is omitted while deleting, all blocklists that match delete request will be deleted regardless of the source type.

## Response `202`

Accepted

## Other responses

- `400`: Bad request
- `401`: Unauthorized
- `403`: Forbidden
- `429`: Too Many Requests
- `500`: Internal Server Error

---

[API](https://skmtc.dev/infobip/apis/infobip-openapi-specification.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification/revisions/9dcbbaf902de?raw)