Scopes error with invalid link

Joe_list
Participant

Our API recently received an error at /properties/v1/contacts/properties

 

{
"status"=>"error",
"message"=>"This app hasn't been granted all required scopes to make this call. Read more about required scopes here: https://developers.hubspot.com/scopes.",
"correlationId"=>"90f4c4bb-4ba4-4a18-a222-2e94904a532d",
"errors"=>[{
"message"=>"One or more of the following scopes are required.",
"context"=>{
"requiredScopes"=>["contacts", "tickets", "e-commerce"]
}}],
"links"=>{
"scopes"=>"https://developers.hubspot.com/scopes"
},
"category"=>"MISSING_SCOPES"
}

First: the link mentioned in the error message is invalid. If I follow it, I get a 404 error.

 

Second: Is this error really meant for the developer? Is there something misconfigured on our part? This really looks like an error that we should be passing along to the user, so that their HubSpot admin can update the permissions for that user.

0 Upvotes
2 Replies 2
dennisedson
Community Manager

hey @Joe_list 

Thank you for bringing that 404 to our attention. Working on setting up a redirect now. 

In the interim, here is a link that it should go to

 

As for the second question, yes, that’s intended for the developer, it means that you’re making a request to an API for which you don’t have the proper scopes. A HubSpot admin updating a user’s permissions won’t add scopes to your OAuth tokens

 

Again, thanks for the notification!

 

best,

Thanks,

Dennis


We are excited to announce that the Community will be launching a weekly newsletter on November 2, 2020!
Sign up today!
0 Upvotes
Joe_list
Participant

hi @dennisedson

 

Thank you for your response. We use oauth tokens for authentication because our app is for external users. When we send the user to HubSpot for authorization, the scopes we request are `contacts` and `timeline`.

 

Is there some reason this endpoint would suddenly also require `tickets` and `e-commerce`?

 

For right now, this seems to be a one-time-only occurrence. It just seems to be an odd error to get when we haven't gotten scopes errors like this before.

 

0 Upvotes