Unable to query the endpoint "crm/v3/properties/notes"

Developer Support APIs & Integrations
1

I have an integration where I first try querying all the fields that the object Note has:

“https://api.hubapi.com/crm/v3/properties/notes”

and then I query all the notes with these properties. It was working fine for a long time, but yesterday I started getting the error:

“You do not have permissions to view object type ObjectTypeId{legacyObjectType=NOTE} in portal 139678070 (requires one of [notes-read])”.

I looked at the list of available scopes in the docs but I cannot find anything of the sort. I also made sure that the user I login with for the OAuth token has every possible permission that I can set via the UI. I still get this error. Can anyone help with this issue? I was unable to find anything related in the changelogs/docs/community posts.

2

Hi @APetrova44,
Thank you for reaching out to the Community!
I’d like to tag in some of our awesome Community Champions to take a look here - @Teun @HubSpot_Corey and @Bortami Do you have any suggestions on this?
Cassie, Community Manager

3

Hi @APetrova44

That error started because Notes now requires the notes-read scope.

It’s a recent change HubSpot split out permissions for engagements like notes, tasks, and calls. Even if your user has full UI permissions, the OAuth app also needs to explicitly request the new scope.

You’ll want to update your app’s authorization URL to include notes-read (and probably notes-write if you’re creating them). Then reauthorize the app so the token is minted with those scopes. Docs here explain the scopes list:

(Working with OAuth - HubSpot docs )

(Accounts Dashboard | HubSpot )

After that, the /crm/v3/properties/notes call should work again. If you’re still blocked, check the app’s scope list in your HubSpot developer account to confirm it’s applied to the installed app

And just as a side note teams that need to keep HubSpot notes and another system always consistent often plug in something like Stacksync. It keeps notes and other CRM objects synced two-ways in real time, so you don’t have to chase scope changes or rebuild around API quirkss

Hope this helps.