# Using Workflow's HTTP Request Action to Work With IdentityNow APIs

**URL:** <https://developer.sailpoint.com/discuss/t/using-workflows-http-request-action-to-work-with-identitynow-apis/7207>\
**Category:** SHF Community Knowledge Base\
**Tags:** workflows, apis\
**Created:** [December 16, 2022, 6:18pm UTC](https://developer.sailpoint.com/discuss/t/using-workflows-http-request-action-to-work-with-identitynow-apis/7207 "2022-12-16T18:18:16Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\
**Post date:** [April 13, 2023, 6:06pm UTC](https://developer.sailpoint.com/discuss/t/using-workflows-http-request-action-to-work-with-identitynow-apis/7207/6 "2023-04-13T18:06:29Z")

</div>

Hi Jesper. Did you create your global security credentials using the `CLIENT_CREDENTIALS` grant type? If so, that is the reason you are seeing a 403. The OAuth client credentials grant type doesn’t have a user context, and therefore can’t access many of our APIs which do require a user context. Furthermore, the HTTP Action in Workflows doesn’t have support for the `AUTHORIZATION_CODE` grant type, which would provide a user context after logging into IDN.

You **must** use a PAT (personal access token) when authenticating to IDN APIs using the HTTP action.

---

_[View the full topic](https://developer.sailpoint.com/discuss/t/using-workflows-http-request-action-to-work-with-identitynow-apis/7207)._