Forum Discussion
Refreshing a web source with an Jira API Key and a dynamic Authorization bearer Token fails
Hi Anonymous,
Thanks for reaching out to the Microsoft fabric community forum.
The error “We found extra characters at the end of the JSON input” typically means that the response Power BI Service is receiving isn’t in a format it can parse as valid JSON. This often happens when the API returns something unexpected, like an error message or HTML instead of proper JSON even if it works fine in Desktop or Postman.
There are few things to check:
* Power BI Service doesn’t handle custom header-based authentication (like a Bearer token added in Power Query)
the same way as Desktop. This can result in the Service not being properly authenticated and receiving an HTML
error page instead of the JSON you're expecting.
* Try copying the actual response (if possible) and pasting it into a JSON validator like jsonlint.com. That will help
confirm whether the data is valid JSON or if something unexpected is coming back.
Regarding the earlier suggestion to wrap the response in "square brackets []", this should only be done if the API is returning multiple top-level JSON objects (which is not typical and usually not the case with the JIRA /search endpoint). The JIRA API normally returns a single JSON object with an issues array inside, so no need to manually wrap it.
One way to make this work reliably is to use an intermediate API layer (like an Azure Function or API proxy) that handles authentication and always returns a clean JSON structure to Power BI. This avoids the Service having to deal with custom headers directly.
I would also take a moment to thank mohitkumawat, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support TeamIf this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi Anonymous,
Thanks for reaching out to the Microsoft fabric community forum.
The error “We found extra characters at the end of the JSON input” typically means that the response Power BI Service is receiving isn’t in a format it can parse as valid JSON. This often happens when the API returns something unexpected, like an error message or HTML instead of proper JSON even if it works fine in Desktop or Postman.
There are few things to check:
* Power BI Service doesn’t handle custom header-based authentication (like a Bearer token added in Power Query)
the same way as Desktop. This can result in the Service not being properly authenticated and receiving an HTML
error page instead of the JSON you're expecting.
* Try copying the actual response (if possible) and pasting it into a JSON validator like jsonlint.com. That will help
confirm whether the data is valid JSON or if something unexpected is coming back.
Regarding the earlier suggestion to wrap the response in "square brackets []", this should only be done if the API is returning multiple top-level JSON objects (which is not typical and usually not the case with the JIRA /search endpoint). The JIRA API normally returns a single JSON object with an issues array inside, so no need to manually wrap it.
One way to make this work reliably is to use an intermediate API layer (like an Azure Function or API proxy) that handles authentication and always returns a clean JSON structure to Power BI. This avoids the Service having to deal with custom headers directly.
I would also take a moment to thank mohitkumawat, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support Team
If this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi Anonymous,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.
Hi Anonymous,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution so that other community members can find it easily.
Thank you.Hi Anonymous,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.