Forum Discussion
Error while creating Access token for Power BI REST API
Hey Anonymous I cannot spot mistakes in you request. My guess would be that you are somehow using an invalid username or password. I therefore suggest either:
- Waiting for someone else opinion
- Authenticate with service principal. Generate a secret for the app you alredy have in your AD and then use the following request:
POST https://login.microsoftonline.com/{{Tenant ID}}/oauth2/v2.0/token
client_id : your client_id
client_secret: the client secret you just generated
grant_type: client_credentials
scope: https://analysis.windows.net/powerbi/api/.default
Be careful, once you generate your app secret, save it, because you will not be able to retreive it again.
Let me know if this solution works for you.
Hi Anonymous Thank you. This method is working and I am generating an access token.
I still have some issues though, that is, when I use this token as Bearer token for REST API, I am getting a 401 Error.
This is the request that I tried with the generated Access Token
access_token=****************************bearertoken=access_tokengatewayId=*********datasourceId=*************Headers={"Authorization": f"Bearer {bearertoken}"}response=requests.request("GET", url=url, headers=Headers)print(response.status_code, response.content)Result comes as - 401 b''Please let me know if the access token I generated by the method you suggested isn't the correct bearer token. If you know how I can generate a bearer token for this purpose, I appreciate your help.Hey Anonymous, I am happy that now is working! You can be sure this is the right way to generate a token to authorize PBI REST API.
The problem here is that you have to setup the right permission in PBI. As you can see from the documentation: Gateways - Get Datasource - REST API (Power BI Power BI REST APIs) | Microsoft Learn there are permission, scope and limitations that you have to take into account.
I never worked with datasource and gateway in PBI so I do not in this specific situation how to set up this permission, but that's the problem you have to solve.
I suggest you to accept the previous solution and open another post, since this is not anymore about an Access Token. I am sure community will help you in setting up the right permission if you will have problems in doing so.
Thanks!