Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
Punith_Nokia
Regular Visitor

Refreshing a web source with an Jira API Key and a dynamic Authorization bearer Token fails

Hello
I have connected powerbi wih web datasource using jira rest API to fetch data from jira and for authentication used Header-Authorization and value- Bearer token key.Refresh works fine in desktop but when published to service and perfrorm dataset manual refresh/schedule refresh/powerautomate flow for refresh, the refresh fails throwing me an error-Data source error: We found extra characters at the end of the JSON input.. The exception was raised by the IDbCommand interface. Table: VAMS_Roadmap.
Cluster URI: WABI-NORTH-EUROPE-redirect.analysis.windows.net
Activity ID: b6f3596a-e523-4bff-8d2d-38ac879d9261
Request ID: d4aa6776-6473-e410-c9d1-f18a881f510d
Time: 2025-04-17 05:18:29Z



Though the API works fine giving json output in desktop/Postman/web browser.Can someone guide me resolve this issue?

1 ACCEPTED SOLUTION
v-mdharahman
Community Support
Community Support

Hi @Punith_Nokia,

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.

View solution in original post

8 REPLIES 8
v-mdharahman
Community Support
Community Support

Hi @Punith_Nokia,

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 @Punith_Nokia,

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 @Punith_Nokia,

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 @Punith_Nokia,

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.

Punith_Nokia
Regular Visitor

https://jiradc2.ext.net.nokia.com/rest/api/2/search?jql=project%20in%20(VAMS)%20AND%20type%20in%20(E..., created, reporter, status, summary,category,customfield_40633, customfield_44152 This is the API I'm using with bearer token connection

v-mdharahman
Community Support
Community Support

Hi @Punith_Nokia,

Thanks for reaching out to the Microsoft fabric community forum.

It looks like you are facing issue with authentication when you are trying to connect your PowerBi with Web Datasource using Jira REST API. As @mohitkumawat already responded to your query, please go through his response and check if it solves your issue.

 

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.

mohitkumawat
Super User
Super User

Hi ,

 

Try adding  [  ] using this parentheses form beginning of line and end of line.

 

Use an online validator like jsonlint.com to validate the structure.

 

 

 

Hi @mohitkumawat 
Thanks for your response, Can you please guide on where exactly I've to use parenthesis?

Helpful resources

Announcements
July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.

Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.