There's a new version of the HubSpot API
As of November 30, 2022, HubSpot API keys are no longer a supported authentication method for accessing HubSpot APIs. Instead, you should use a private app access token or OAuth to authenticate API calls. Learn more about this change and how to migrate an API key integration to use a private app instead.
HTTP Methods:
DELETE
Response Format:
json
Requires Authentication?
Yes
Rate Limited?
Headers
Products:
Marketing & CRM
crm.objects.contacts.write
Delete an existing contact from a particular HubSpot portal.
If a contact with the same email address interacts with the portal again (via a form submission for example) the contact will be added back into the user interface.
Required Parameters | How to use | Description |
---|---|---|
OAuth access token or private app access token | Authorization: Bearer {token} header | Used to authenticate the request. Please see this page for more details about authentication. |
Contact ID | Used in the request URL | You must pass the Contact's ID that you're deleting in the request URL. See the example URL below for an example of this. |
Optional Parameters | How to use | Description |
---|---|---|
None | None | No optional parameters for this method. |
Example URL: https://api.hubapi.com/contacts/v1/contact/vid/61571
If the request succeeds, you'll get an HTTP 200 response with a JSON object, which represents that you've just deleted the contact out of the system.
The response from this API call are standard REST-style HTTP response codes that mark success or failure, with meta information about the call that was made. There will be no data in the response body.