topic Re: Postman 3-legged auth error in BIM 360 API Forum

Postman 3-legged auth error

Charlie_Portelli_PHZAJ8NNHFJA — Wed, 05 Jul 2023 20:01:52 GMT

I've created a postman request using this url: https://developer.api.autodesk.com/authentication/v2/authorize

I've followed the steps found on this link. I'm able to get the BIM 360 login screen to appear and enter my credentials and it seems to save the new access token. When I click SEND in postman to execute the request I get the error below

"developerMessage": "The client_id specified does not have access to the api product",

"moreInfo": "https://forge.autodesk.com/en/docs/oauth/v2/developers_guide/error_handling/",

"errorCode": "AUTH-001"

I've confirmed in my aps apps that the client_id does have access to all the aps api's. Any thoughts?

Re: Postman 3-legged auth error

rbigare — Tue, 31 Oct 2023 11:58:32 GMT

Hi Charlie -

Did you get anywhere with this ? Having the same problem on our hand.

Re: Postman 3-legged auth error

sevfitzgerald — Tue, 31 Oct 2023 19:42:44 GMT

Hello,

I am also running into this same error in Postman after updating to suit the v2 Authentication endpoints according to the APS documentation.

Have either of you had any progress?

Re: Postman 3-legged auth error

rbigare — Wed, 01 Nov 2023 09:56:51 GMT

Yes,

There were two problems we had to solve.
1) Our encrypted Base64 client id was being pushed as encrypted to the header parameters, we had to decode it as string before adding to the header
2) You need BIM 360 integration turned on for all the hubs you want to work on. Autodesk has separate settings and integration for EMEA / US etc

In your case it could be something else. But would recommend double checking all parameters (client id, secret, redirect http etc)

Hope this helps

Re: Postman 3-legged auth error

Crashnorun — Mon, 26 Feb 2024 15:23:28 GMT

Just last week I came across this site that explained the process a bit better:

https://aps.autodesk.com/blog/using-3-legged-oauth-v2-postman