Classic file types are no longer available for use as of January 2021. You can transition your classic files or download a PDF. Learn More

How to setup API to import Wdesk reports data into Power BI?

Answered
Request Demo

I have setup the user and got client ID & secret. I am stuck on authentication step to get the bearer token?

How do I issue POST reuest? which tool to use or is there any query that I can run in powerBI to get data which will authenticate the client id & secret?

 

0

Comments

3 comments

Date Votes
  • Jeff Hickey

    Hello Vinit. The Client ID and Client Secret that is generated when creating an OAuth2 Grant in Workiva can be passed to the Identity and Access Management (IAM) API to retrieve a bearer token. The bearer token is then used to authenticate with subsequent Workiva API calls. Developer documentation for the IAM API is located at https://developers.workiva.com/workiva-iam/reference and developer Wdata API documentation is located at https://developers.workiva.com/workiva-wdata/reference. Workiva does not require a specific tool or programing language. Any tool or language that you prefer and that can interface with the API is acceptable.

    Alternatively, Wdata Chains can be used to build an integration between Power BI and Workiva. A high level overview of Chains can be found here www.workiva.com/wdata/connectors along with technical documentation here https://support.workiva.com/hc/en-us/categories/360002307351-Working-in-Wdata. The Chain's Power BI connector does require an "Application (Client) ID" to be properly configured. This is the Azure application's client ID which is different and separate from the Workiva Client ID generated by the OAuth2 Grant.

    0
  • Vinit Malviya, CISA
    • Edited

    Hi, 

    I am trying to get bearer token through post request in python but it is giving error message 403 - Missing Authentication Token. Below is the screenshot of the code.

     

    Please resolve this.

     

    Thanks,

    Vinit

    0
  • Jeff Hickey

    Hi Vinit, it looks like you have added greater than and less than characters ('<', '>') around your client_id and client_secret which is invalid. Try it again without those characters. You can get a valid client ID and client secret pair from your OAuth2 Grant.

    0

Please sign in to leave a comment.