Align Archive Endpoint Behavior in HubSpot V3/V4 API with Legacy API

JavaScript must be installed and enabled to use these boards. Your browser appears to have JavaScript disabled or does not support JavaScript. Please refer to your browser's help file to determine how to enable JavaScript.

HubSpot Ideas

Search HubSpot Ideas or Create Idea

Status:

Hello,

I am encountering an issue with the HubSpot V3 and V4 API. When hitting the archive endpoint for the CRM Objects or Associations, we always receive the 204 No Content status code regardless of whether the request was successfully executed or whether a nonexistent ID was set to be archived.
In contrast, the Legacy API returns a 404 Not Found status for IDs that are already archived or do not exist.

Would it be possible to change the behavior to match that of the Legacy API?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Reply to Idea