Delete Contact

curl --request DELETE \
  --url https://api.example.com/api/v1/contact-lists/{listId}/contacts/{id}

DELETE

api

contact-lists

{listId}

contacts

{id}

Delete Contact

curl --request DELETE \
  --url https://api.example.com/api/v1/contact-lists/{listId}/contacts/{id}

Permanently delete a contact from a list.

This action is irreversible. Consider suppressing the contact instead if you want to preserve their history.

Path Parameters

listId

string

required

The unique list ID (e.g., lst_abc123).

string

required

The unique contact ID (e.g., cnt_abc123).

Examples

import { MailBreeze } from "mailbreeze";

const mailbreeze = new MailBreeze({ apiKey: "sk_live_xxx" });
const contacts = mailbreeze.contacts("lst_abc123");

await contacts.delete("cnt_abc123");

console.log("Contact deleted");

Response

Returns 204 No Content on success with no response body.

Errors

Code	HTTP Status	Description
`CONTACT_NOT_FOUND`	404	Contact with this ID doesn’t exist
`LIST_NOT_FOUND`	404	List with this ID doesn’t exist

When to Delete vs Suppress

Action	Use Case	Email History	Can Re-subscribe
Delete	Remove completely, GDPR requests	Lost	Yes (as new contact)
Suppress	Stop emails but keep history	Preserved	Yes (with status change)

For GDPR deletion requests, use delete. For unsubscribes or bounces, use suppress to maintain deliverability history.

Update Contact Suppress Contact

Documentation Index

​Path Parameters

​Examples

​Response

​Errors

​When to Delete vs Suppress

Path Parameters

Examples

Response

Errors

When to Delete vs Suppress