APIs & Integrations

sgeorgiev
Member

Error calling API - Request for Integration Permissions

Hello,

 

When I am testing my connection in the OAuth 2.0 Playgroud I keep getting the following error "Request for Integration Permissions. Couldn’t complete the connection The redirect_uri does not match the client registered   redirect_uri. Please contact the integrator." at the 1st step.

I am most certain it has to do something with the scopes in the redirect_uri but had no luck finding the issue on my own.

My developer portal ID is 7972847 and my app ID is 222831.

 

I would be very grateful to every one that helps.

 

Best regards,

Stanislav

 

 

 

0 Upvotes
4 Replies 4
Willson
HubSpot Employee
HubSpot Employee

Error calling API - Request for Integration Permissions

Hey @sgeorgiev,

 

I am not sure what value you're currently passing but can you ensure the redirect_uri value you're passing is the following:

https://www.getpostman.com/oauth2/callback

I hope this helps!

Product Manager @ HubSpot
0 Upvotes
sgeorgiev
Member

Error calling API - Request for Integration Permissions

Hey @Willson,

 

Yes this is what I'm passing at the moment.

I was using localhost but decided to run it in postman as well.

0 Upvotes
sgeorgiev
Member

Error calling API - Request for Integration Permissions

Hey @Willson 

 

This is the error I get when attempting to get new access token in both OAuth 2.0 Playgroud and Postman.

hubDevToolsErrorhubDevToolsError

Is this a common issue and could you please give an idea how to tackle it?

 

Stanislav

 

0 Upvotes
Willson
HubSpot Employee
HubSpot Employee

Error calling API - Request for Integration Permissions

Hey @sgeorgiev 

 

Taking a look into this, you're receiving a 400 response code. When making a request to our APIs specifically around OAuth, we should be seeing a response like the following:

If there are any problems with the request, you'll receive a 400 response with an error message.
{
  "status": "EXAMPLE_ERROR_CODE",
  "message": "A human readable error message",
  "correlationId": "da1e1d2f-fa6b-472a-be7b-7ab9b9605d59",
  "requestId": "ecc0b50659814f7ca37f5d49cdf9cbd3"
}

Given that you attempted this in Postman, we'd expect to see a more detailed response as to what is causing the issue. Can you attach the error response seen in Postman too?

 

If possible, could you provide the Request URL and payload being sent when making the request to our OAuth APIs.

 

Thanks!

Product Manager @ HubSpot
0 Upvotes