Calls to retrieve custom objects are now returning 403 forbidden results when calling endoints such as https://api.hubapi.com/crm/v3/objects/[objectType]?limit=100. We are using private app integration with an access token setup. This error started occuring somewhere between Jan 21, 2024 (last recorded successful call), and Feb 5 (first recorded error). The error message is very general paired with a 403 status code. See postman result below
{
"status": "error",
"message": "There was a problem with the request.",
"correlationId": "179669fd-2073-4adb-9321-399b329e13e1"
}
Calls to https://api.hubapi.com/crm/v3/schemas still succeed.
Important data points
- Both the above calls use the same access token
- Scopes for this private app havn’t changed, and include crm.objects.custom.writecrm.objects.custom.read
- Can successfully generate 403 codes for inccorect scopes if a different access token from another one of our private apps is used with the custom object call
- As far I can tell the api documentation hasn’t changed for custom objects Accounts Dashboard | HubSpot
We have not altered the structure of our programatic calls or rotated our access token during this window. This leads me to believe something has changed on the Hubspot side that is not reflected in the documentation. Any help or advice would be helpful.