Currently Web.Headers only returns generic response headers. Most APIs return paging information(count, start,end) in response headers. Exposing custom response headers would significantly speed up integration of APIs to feed data in Power BI
4 Comments
+1 on this. The Shopify REST api, for example, sends back pagination information in the header. Since it is filtered out but needed, you have to develop a custom connector, which then requires a Gateway.
If the response headers were available, this could all be done without need of a connector.
+1 for me too. I need to connect to my CMDB ( Spider) API, the authentication token is return within the response header. Since only a subset of the header is return, I have to create a custom connector to authenticate to the API and download the information into PowerBI.
- Status added:New
- Let me paginate PLEASE
Recent ideas
Allow Power BI subscriptions to use a no-reply sender instead of the subscription owner's mailbox
Following the migration to the new email delivery platform, subscription emails now appear to come from the subscription owner. This generates large volumes of Out of Office replies, auto-replies, an...
