Skip to main content
DELETE
Endpoint Alias: You can also use /api/v1/records instead of /api/v1/leads. Both endpoints are functionally identical - use whichever naming convention fits your integration.

Lead Lookup

Leads are identified by externalId or phoneNumber, not internal IDs. This matches how you created the lead.
At least one of phoneNumber or externalId is required. If both are provided, externalId takes priority for the lookup.

Authentication

string
required
Your API key with write scope

Query Parameters

string
required
The ID of the campaign the lead belongs to
string
Phone number in E.164 format (e.g., +15555551234).Required if externalId is not provided.
string
Your CRM’s internal ID for this lead.Required if phoneNumber is not provided.

Response

boolean
Whether the request was successful
object
string | null
Error message if request failed

Examples

Delete by external CRM reference:

Notes

Permanent Deletion: This action cannot be undone. The lead will be permanently deleted.
Need the lead data? The delete response only confirms deletion—it doesn’t return the lead’s details. If you need the lead information (metadata, status, etc.), fetch the lead first using GET /api/v1/leads, then delete it.
URL Encoding: When passing phone numbers in the URL, remember to URL-encode the + sign as %2B.
Access Control: You can only delete leads that belong to campaigns your API key has access to.

Common Errors