Power BI REST API's

[david_busint]

Hi all,

When I use the below Power BI/Fabric REST API's I've getting odd behaviour in terms of the data that gets returned. 

A-  GET https://api.powerbi.com/v1.0/myorg/admin/groups?$top={$top}

B - GET https://api.powerbi.com/v1.0/myorg/groups

C - GET https://api.fabric.microsoft.com/v1/admin/workspaces/{workspaceId}

In terms of results...

A - The Power BI non-admin returns all of the workspaces which I have access to as I would expect.

B - The Power BI admin version of the API doesn't include any of the more recently created workspaces even though I'm an admin.

C - The Fabric admin API returns all of the workspaces. 

I'm speculating that the issue is that more recently created workspaces aren't being returned by the Power BI admin group API (B) because of some issue with how it interacts with the post-Fabric environment?

Has anyone else run into this issue and have you found a solution? I can't see any obvious difference in the workspaces that could be causing this issue and there isn't anything in the API documentation that to explain why the Power BI Admin group API doesn't work for more recently created workspaces. 

Yes I could use the Fabric API but I'm finding them very limited when it comes to getting the kind of information that is available in the Power BI API's.

Kind regards,

David

[v-nmadadi-msft]

Hi  @david_busint ,
Thanks for reaching out to the Microsoft Fabric Community forum.

The $top query parameter constrains the maximum number of workspace records returned in the API response. It acts as a server-side limit on the result set size for the request, allowing callers to control the volume of data retrieved in a single call. As you are using top query parameter in API call, that may be the reason why the API may not be returning complete workspace list, as a troubleshooting step please try testing it without the top parameter and check the list.

I hope this information helps. Please do let us know if you have any further queries.
Thank you

[david_busint]

Hi v-nmadadi-msft,

I've already considered that and adjusted the limit to far above the required value but thank you for the suggestion.

Kind regards,

David

[v-nmadadi-msft]

Hi @david_busint ,

Thank you for the update,

Please try calling the API with the $skip parameter to paginate through the results,

as this can help ensure you are not missing any workspaces when the total count exceeds the default response size. Additionally, as a troubleshooting step, you can use the $filter parameter to narrow the results and specifically target the most recently created workspace. This can help validate whether newly created workspaces are being returned correctly by the API and rule out any issues related to pagination or result ordering.

I hope this information helps. Please do let us know if you have any further queries.
Thank you