Delete Contact
Delete an existing contact from your Bulkit account.
Last updated · Markdown version
HTTP method and path
HTTP
DELETE /api/v2/contacts/:idAuthorization requirements
This endpoint supports:
- Bearer token (recommended):
Authorization: Bearer <your_api_token> - Legacy headers:
X-API-KeyandX-API-Secret - URL query parameter:
?apikey=<your_api_token>
Authorization example
HTTP
Authorization: Bearer bk_live_8n6JQv3K1h9Lp0MdParameters
| Parameter | Location | Required | Type | Description |
|---|---|---|---|---|
id | Path | Yes | string / integer | Contact ID or UUID to delete |
Authorization | Header | Yes (recommended) | string | Bearer <your_api_token> |
X-API-Key | Header | Optional (legacy) | string | Your Bulkit key |
X-API-Secret | Header | Optional (legacy) | string | Your Bulkit secret |
apikey | Query | Optional fallback | string | API key used in URL authorization |
Request examples
cURL / Bash
curl -X DELETE "https://api.bulkitsms.com/api/v2/contacts/442" \
-H "Authorization: Bearer bk_live_8n6JQv3K1h9Lp0Md"Success response example
JSON
{
"status": "success",
"message": "Contact deleted successfully"
}Error response examples
JSON
{
"status": "error",
"message": "Invalid credentials"
}JSON
{
"status": "error",
"message": "Contact not found"
}Notes
- delete operations are scoped to the authenticated account
- deleting a contact removes it from future contact-based send workflows