Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now

Reply
bhayden
New Member

InvalidRequest: Resource access type View unsupported for Reports

We have a website that displays embedded PowerBI reports.  The website, the code that drives it, and the reports themselves have not changed in months.  This week, the PowerBI API call to generate our embed tokens started refusing to give it to us, instead returning this error:

 

Client error: `POST https://api.powerbi.com/v1.0/myorg/groups/<our-id>/reports//GenerateToken` resulted in a `400 Bad Request` response

InvalidRequest: Resource access type View unsupported for Reports

 

I can't find anything online about this error.  What could be suddently causing this?

1 ACCEPTED SOLUTION

It turns out the endpoint we are using is fine.  Microsoft themselves have example code using this endpoint for View operations.

 

The problem ended up being a very subtle change on Microsoft's side where a json field name was changed from "Name" to "name", which broke a case-sensitive field lookup in our code.

View solution in original post

2 REPLIES 2
AmosHersch
Microsoft Employee
Microsoft Employee

Hi,

 

I'm not sure what have changed in Power BI side, but can you please explain why you call this specific endpoint? According to the documentation it should only be used when generating an embed token to be used for creating reports Embed Token - Reports GenerateTokenForCreateInGroup - REST API (Power BI Power BI REST APIs) | Micro...

That's probably why you get an error when you specify "accessLevel"="view" in the request. I believe only "Create" is supported.

If you're just embedding existing report\s you should use a different endpoint like this one Embed Token - Generate Token - REST API (Power BI Power BI REST APIs) | Microsoft Docs

It turns out the endpoint we are using is fine.  Microsoft themselves have example code using this endpoint for View operations.

 

The problem ended up being a very subtle change on Microsoft's side where a json field name was changed from "Name" to "name", which broke a case-sensitive field lookup in our code.

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

February Power BI Update Carousel

Power BI Monthly Update - February 2026

Check out the February 2026 Power BI update to learn about new features.