Saltar al contenido principal
DELETE
/
v1
/
contacts
/
{contactId}
# Delete a specific contact by ID
curl -X DELETE "https://api.contactship.ai/v1/contacts/c1a2b3c4-d5e6-f7g8-h9i0-j1k2l3m4n5o6" \
  -H "x-api-key: your-api-key"

// 204 No Content - No response body

Documentation Index

Fetch the complete documentation index at: https://docs.contactship.ai/llms.txt

Use this file to discover all available pages before exploring further.

This endpoint allows you to permanently delete a contact from your organization’s database. This action cannot be undone, so use it with caution.

​
Use Cases

  • Remove obsolete or duplicate contact records
  • Comply with data retention policies
  • Honor user requests to delete their personal information
  • Clean up your contact database

​
Path Parameters

​
contactId
string
requerido
The unique identifier of the contact to delete. This is a UUID string that was generated when the contact was created.

​
Headers

​
x-api-key
string
requerido
Your API key for authentication. You can find this in your dashboard under API settings.

​
Response

​
status code
number
204 on success (No Content)
This endpoint returns a 204 No Content response on successful deletion, with no response body.

​
Error Codes

  • 400 Bad Request - Invalid contact ID format
  • 401 Unauthorized - Invalid or missing API key
  • 404 Not Found - Contact not found
  • 500 Internal Server Error - Server-side error

​
Code Examples

# Delete a specific contact by ID
curl -X DELETE "https://api.contactship.ai/v1/contacts/c1a2b3c4-d5e6-f7g8-h9i0-j1k2l3m4n5o6" \
  -H "x-api-key: your-api-key"

// 204 No Content - No response body

​
Notes and Best Practices

  • Always confirm with the user before permanently deleting a contact
  • Consider implementing a “soft delete” in your application by flagging contacts as inactive instead of permanently deleting them
  • Keep audit logs of deleted contacts for compliance purposes
  • Ensure you have proper error handling for failed deletion attempts
  • If you’re deleting contacts as part of a bulk operation, implement rate limiting to avoid API throttling