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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
pratheeban
Frequent Visitor

Get Reports REST api not working - Showing 400 Bad Request

Hi All,

 

I am trying to retrieve the report metadata using the REST API provided,

https://docs.microsoft.com/en-us/rest/api/power-bi/reports/getreportingroup

 

REST call tried: https://api.powerbi.com/v1.0/myorg/groups/f702bdb7-e372-4990-a828-5e5449c6f676/reports/7d36d8aa-4ae8...

 

All the REST calls are working fine, except above not sure what I'm doing wrong.... Please help me understand this.

 

Thanks

9 REPLIES 9
luismangahr
Regular Visitor

I have exactly the same problem. Did you make any progress?

 

Just to clarify to others: App is registered, I have the access token and I can use it for all the other calls. For example, I can successfully perform this request:

  

GET https://api.powerbi.com/v1.0/myorg/groups/{groupId}/reports

  

In the response I get the list of reports. If I pick one specific report id and I just by add it to the URL path in the previous request, I get the "400 Bad Request" response...

 

GET https://api.powerbi.com/v1.0/myorg/groups/{groupId}/reports/{reportKey}

 

Hi All,

 

I did not get any solution to the problem.

 

Thanks

I am having the exact same problem. I get an HTTP 400 Bad Request response from the API even though I am passing in the GroupId and the ReportId correctly. All other APIs are working. For example Get Reports in Group (https://api.powerbi.com/v1.0/myorg/groups/{{groupId}}/reports) work as expected. However when I try and use Get Report in Group (https://api.powerbi.com/v1.0/myorg/groups/{{groupId}}/reports/{{reportId}}) I get back an HTTP 400. I am using Postman to test this and I can confirm that I have double checked the GroupId and ReportId.

 

I also have all permissions assigned to my specific user. Something is wrong with this AI endpoint,

 

UPDATE: This has been brought up in the Developer forum and it is indeed a bug. The workaround (and I have verified it works in Postman) is to add the Header "Accept" and set it's value to "none".

Anonymous
Not applicable

Workaround works:

 

Add the Header "Accept" and set it's value to "none"

Anonymous
Not applicable

I am also having the same issue. Application has been registered. Not a permissions issue.

v-shex-msft
Community Support
Community Support

Hi @pratheeban,

 

You need to set up permission before your invoke rest api, I don't think power bi service will allow anonymous authorization to get specific power bi contents.

Register an Azure AD app to embed Power BI content

 

Regards,

Xiaoxin Sheng

Community Support Team _ Xiaoxin
If this post helps, please consider accept as solution to help other members find it more quickly.

Hi,

 

Thanks for the reply!

 

I did register the application. All the other REST calls are working Except this... (Showing 400 Bad request).. 

 

Not sure what I'm missing here. Pls let me know

 

Thanks

Not sure if there is any syntax mistake but I have used as per the documentation... Please help me understand that.

 

Thanks

Hi @pratheeban,

 

I'd like to suggest you post to develop forum to get better support.

 

Regards,

Xiaoxin Sheng

Community Support Team _ Xiaoxin
If this post helps, please consider accept as solution to help other members find it more quickly.

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors