Account configuration error - OBJECT_NOT_FOUND

We have a user/account we’re integrated with that’s receiving errors when we attempt to use the HubSpot API. From what I gather there’s something odd about how their HubSpot instance is configured, but we’re not sure what.

The path used when receiving this error is https://api.hubapi.com/contacts/v1/contact/vid/${contactId}/profile, this URL isn’t returning any issues outside of this particular account. Our integration is making these API calls.
I’m receiving the following error response on 03/27/2024 at 20:32 UTC.
Endpoint https://api.hubapi.com/contacts/v1/contact/vid/${contactId}/profile

{ “status”: “error”, “message”: “contact does not exist”, “correlationId”: “7547f655-ecbe-48d6-9afc-b483dbf6b583”, “errors”: [ { “message”: “The contact 6829045884 does not exist.” } ], “category”: “OBJECT_NOT_FOUND” }

One thing I did with this user is setup a fresh HubSpot instance, and this error did not persist. Is there any reason why this OBJECT_NOT_FOUND error would be returned if when we’re confirmed inputting valid data?


@Kovon wrote:

We have a user/account we’re integrated with that’s receiving errors when we attempt to use the HubSpot API. From what I gather there’s something odd about how their HubSpot instance is configured, but we’re not sure what.

The path used when receiving this error is https://api.hubapi.com/contacts/v1/contact/vid/${contactId}/profile, this URL isn’t returning any issues outside of this particular account. Our integration is making these API calls.
I’m receiving the following error response on 03/27/2024 at 20:32 UTC.
Endpoint https://api.hubapi.com/contacts/v1/contact/vid/${contactId}/profile

{ “status”: “error”, “message”: “contact does not exist”, “correlationId”: “7547f655-ecbe-48d6-9afc-b483dbf6b583”, “errors”: [ { “message”: “The contact 6829045884 does not exist.” } ], “category”: “OBJECT_NOT_FOUND” }

One thing I did with this user is setup a fresh HubSpot instance, and this error did not persist. Is there any reason why this OBJECT_NOT_FOUND error would be returned if when we’re confirmed inputting valid data?


This issue can arise due to various reasons such as incorrect contact ID, deleted contact, synchronization issues, insufficient permissions, configuration discrepancies, or API rate limits. To resolve this error, it’s essential to verify the accuracy of the contact ID, check for any recent deletions or synchronization issues, ensure proper permissions and configuration settings, and monitor API usage to avoid hitting rate limits.