Data from Web API do not refresh in PBI Service

[xichiza]

Hi Everyone,

I have imported data from an web API as in the screenshot below. Everything is working good on PBI Desktop and I am able to get data.

However, when publishing on PBI Service and trying to refresh Data, I am getting this issue with data credentials : 

Does anyone know how to get data refreshed in PBI Service ? 

Thanks !

[Anonymous]

Hi @xichiza 

Please see the answer in the below link.

https://community.powerbi.com/t5/Service/Refreshing-data-from-REST-API-works-on-Desktop-fails-on-Ser...

Your api is using api-key autentication which is not currently directly supported by PowerBI service. Bcoz PowerBI Service only allow API autentication with anonymus , Windows and Basic

The workaround is to use a Gateway and Skip Test Connection 

https://community.powerbi.com/t5/Community-Blog/Power-BI-Gateway-Monitoring-amp-Administrating-Part-...

Best Regards

Community Support Team _ Polly

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi @xichiza ,

Please refer to the following document to see if it helps you.

https://docs.microsoft.com/en-us/power-bi/connect-data/service-admin-troubleshooting-power-bi-person...

Error: The credentials provided for the dataset are invalid. Please update the credentials through a refresh or in the Data Source Settings dialog to continue.

Solution: If you get a credentials message, it could mean:

• The usernames and passwords that you used to sign in to data sources aren't up to date. In Power BI, go to refresh settings for the dataset. In Manage Data Sources, select Edit credentials to update the credentials for the data source.

• Mashups between a cloud source and an on-premises source, in a single query, fail to refresh in the gateway (personal mode) if one of the sources is using OAuth for authentication. An example of this issue is a mashup between CRM Online and a local SQL Server instance. The mashup fails because CRM Online requires OAuth.

  This error is a known issue, and it's being looked at. To work around the problem, have a separate query for the cloud source and the on-premises source. Then, use a merge or append query to combine them.

Best Regards

Community Support Team _ Polly

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.