Forum Discussion
Power BI Admin API parameters
Hi! This is a known gap in the Admin API and subscription parameters are not exposed here. Paginated report subscriptions are fundamentally different from standard report subscriptions — each subscription can be configured with a distinct set of parameter values, which is the whole point of using them for data-driven delivery. But the Admin API was designed around standard reports first, and this parameter context was never added to the subscription response schema.
Microsoft's subscription APIs were built for governance/auditing use cases (who is subscribed to what, is it enabled, how often) rather than for inspecting the full delivery configuration of paginated report subscriptions. The parameters field has been a community-requested addition for some time but hasn't shipped.
Your workaround options
Unfortunately none are perfect:
- XMLA / TOM endpoint — If your paginated reports are in a Premium/Fabric workspace, you can query the XMLA endpoint for report metadata, but this still won't give you per-subscription parameter values.
- Power BI REST API — Get Report Pages — Doesn't help with subscription parameters either.
- Fabric Metadata Scanning APIs (/admin/workspaces/modified + /admin/workspaces/getInfo) — These give you richer item-level metadata than the subscription API, but paginated report parameter configurations within subscriptions are still not surfaced.
- Direct database approach (if on Fabric) — If your paginated reports are running on Fabric capacity, the subscription configuration including parameters is stored internally, but there's no supported way to query it directly.
- Manual export + parsing — Some teams export subscription configs from the Power BI service UI and parse them, but this doesn't scale.
Thanks for the reply. Can you please clarify :
- XMLA / TOM endpoint — If your paginated reports are in a Premium/Fabric workspace, you can query the XMLA endpoint for report metadata, but this still won't give you per-subscription parameter values. For this- I think what you meant is if a report subscription has parameters , this will not give us what values are passed in each subscription correct?
- For #4 - where is the report parameters stored?
- for the last one - Manual export + parsing — "Some teams export subscription configs from the Power BI service UI and parse them, but this doesn't scale"- can you provide more informaiton on which UI to be called? Is it available as a API that we can call using Alteryx and parse them?
Thank you again!
Unfortunately none are good, reliable, or efficient solutions. I should have really left 1-4 of because they can't really be accessed. For #5, I have never done it myself but have heard of teams trying to do this:
- Manage Subscriptions page — As a Power BI admin, you can go to the Admin Portal → Subscriptions, which gives you a list view of subscriptions across the tenant. This is UI-only though, there's no export button natively.
- Per-report subscription view — Opening a paginated report and going to Subscriptions shows you each subscription with its parameters configured. Again, UI only.
- Browser DevTools network capture — This is where the "parsing" part comes in. When you load the subscriptions management page, Power BI makes background API calls to retrieve the subscription data. You can:
- Open Chrome DevTools → Network tab
- Navigate to the subscriptions page for a report
- Intercept the raw API response which often contains more fields than the documented public API returns, sometimes including parameter values
- Copy that JSON payload out manually
You can also go to the submit ideas page and look for ideas that you can vote on in hopes of Msft shipping them to prod, and or add your own: Fabric Ideas - Microsoft Fabric Community
