Chiranjiv Rathod on Mon, 11 Mar 2019 05:12:32


We need to use Secured REST API resource as SSRS data source.

We couldn't find a way to call Secured REST resource from SSRS. 

Additional information related to these are, we need to pass bearer token to REST resources since they are secured and need to authorized before access. We couldn't find a way to do the same in SSRS.

Highly appreciate if you can help on us to resolve this issue.



Lukas DreiKlein on Mon, 11 Mar 2019 08:18:04

Hi Chiranjiv Rathod,

About your request, you could check the REST Api function in SSRS2017 in these two links:

  1. How to read REST API in SSRS Reports
  2. SQL Server Reporting Services Rest API



Chiranjiv Rathod on Wed, 13 Mar 2019 04:57:09


My problem is still remain same.

Report Server should authorize my REST API used as Report Data Source 


Lukas DreiKlein on Thu, 14 Mar 2019 09:36:52

Hi Chiranjiv Rathod,

I have consider your request for a while and I came to three conclusions,

1. It seems it's not very easy for SSRS to pass token and get the data so directly. I haven't find any supportive way. Maybe we could try C# script which can pull the data through rest.api, then pass the value to ssrs, but I am no expertise with this, just think it would be a choice.

2.  We could also choose third party OBDC driver like I mentioned in  

How to read REST API in SSRS Reports (JSON / XML / Call SOAP Web Service)

3. We could try Power BI which already has this kind of function, and can be easily achieved. See in:

Using a REST API as a data source

Also if your want SSRS add similar function in the future, you could submit the requirement at

If the requirement mentioned by customers for many times, the product team may consider to add this feature in the next SQL Server version. Your feedback is valuable for us to improve our products and increase the level of service provided.

Best Regards,


MSDN Community Support Please remember to click Mark as Answer; the responses that resolved your issue, and to click Unmark as Answer if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact