Remove a contact detail from a lead Run in API Explorer

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://apidocs.plannrcrm.com/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json 
{
  "PlannrCRM MCP server": {
    "url": "https://apidocs.plannrcrm.com/mcp"
  }
}
Close
DELETE /api/v1/leads/{lead_uuid}/contact-details/{uuid}
Personal access token & O auth2

Detaches the contact detail from the lead and soft deletes it only when no other lead or account is linked to it. Removing the primary of a type promotes the oldest remaining contact detail of that type. A lead must keep at least one email address or phone number.

Path parameters

  • lead_uuid string Required

    The UUID of the lead.

  • uuid string Required

    The UUID of the contact detail.

Responses

  • 403 application/json

    Unauthorized

    Hide response attribute Show response attribute object
    • message string Required

      A human-readable description of the error.
  • 404 application/json

    Lead belongs to another firm or the contact detail to another lead

    Hide response attribute Show response attribute object
    • message string Required

      A human-readable description of the error.
  • 409 application/json
    Hide response attribute Show response attribute object
    • message string Required

      A human-readable description of the error.
  • 422 application/json

    Validation error

    Hide response attributes Show response attributes object
    • message string Required

      A human-readable description of the error.

    • errors object

      Validation messages keyed by the field that failed.

      Hide errors attribute Show errors attribute object
      • * array[string] Additional properties
DELETE /api/v1/leads/{lead_uuid}/contact-details/{uuid} 
curl \
 --request DELETE 'https://api.plannrcrm.com/api/v1/leads/53f22fe4-3731-4cdc-aa12-e65bd0b15e52/contact-details/6a6a176d-52bc-47f2-88c3-141d44059bcf' \
 --header "Authorization: Bearer $ACCESS_TOKEN"
Response examples (403) 
{
  "message": "This action is unauthorized."
}
Response examples (404) 
{
  "message": "Not Found"
}
Response examples (409) 
{
  "message": "This lead has been promoted to a client and is locked."
}
{
  "message": "This lead is archived and cannot be changed."
}
Response examples (422) 
{
  "message": "A lead must keep at least one email address or phone number.",
  "errors": {
    "contact_detail": [
      "A lead must keep at least one email address or phone number."
    ]
  }
}