Can't Refresh without Gateway with Web API Source

[Anonymous]

I'm working on analyzing some Jira data for my company. Since we use Jira On Premise, the Jira Power BI app doesn't work, and instead I'm using the REST API. My query works within Power BI Desktop, and will correctly display in Power BI Service. However, I cannot refresh the data (neither manually nor through scheduled refresh). I'm getting the following error:

According to this post, Web sources don't seem to be enabled for refresh. However, the post is old and they mentioned they were working on it. Also, my error is about credentials, not just refresh. As you can see the credentials menu is grayed out, so I can't access it. In Power BI Desktop, my credentials are Basic with a Privacy Level of None.

I use a function and a query for my data. I know this can cause issues, but I believe I've followed this guide properly. Here are the function and the query:

Appologies for the blocked out sections. They are mostly organizational commands and are hidden to keep field names from showing.

Please help me figure out what is causing this error and ultimately how I can enable scheduled refreshing for this dataset. Thanks!

[ExcelNorge]

We have got an update from our Product Engineering team:

As we see that the User is using https and http urls to build the report. We checked with our SME they confirmed that, Power BI Service requires https urls for Web data sources to refresh. For non-secured urls (http), it's required to go through the gateway. By design.

So an anonymous API feed using "http" will not allow for a scheduled refresh in the online Power BI service without a gateway. It needs to be an https one.

[GilbertQ]

Hi there

From the error it appears that it is coming from not being able to authenticate back to your source data.

Are you using the On-Premise Data Gateway in Enterprise or Personal Mode?

[Anonymous · Accepted solution]

Thanks for the response! Actually, I am not using a Gateway at all. I wanted to just be able to use the web source from the web. However, I figured out that the actual problem stemmed from the fact that the web API was on-premise too and not on the open internet, which is why a Gateway is required.

[GilbertQ]

Thanks for letting us know what was the cause and how you got it resolved. It is sure to help others.