# Users API 403 E0000005 response

**URL:** <https://devforum.okta.com/t/users-api-403-e0000005-response/16731>\
**Category:** API\
**Tags:** api\
**Created:** [October 25, 2021, 9:45pm UTC](https://devforum.okta.com/t/users-api-403-e0000005-response/16731 "2021-10-25T21:45:39Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![sdunning](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/sdunning/32/2161_2.png) [@sdunning](https://devforum.okta.com/u/sdunning)\
**Post date:** [October 25, 2021, 9:45pm UTC](https://devforum.okta.com/t/users-api-403-e0000005-response/16731/1 "2021-10-25T21:45:39Z")

</div>

When calling `https://{{OKTA_DOMAIN}}/api/v1/users/{{login}}` via Postman I am able to successfully retrieve the user information.

When calling the same URL in NodeJS (NestJS/Axios) passing the same `SSWS {{apikey}}` Authorization header used in the Postman request I receive the following response

```auto
{ errorCode: 'E0000005',
        errorSummary: 'Invalid session',
        errorLink: 'E0000005',
        errorId: 'oaeNap_mXcbTcyCF5Xxm3ifMw',
        errorCauses: [] }

```

---

<div class="post-metadata">

**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\
**Post date:** [October 26, 2021, 12:05am UTC](https://devforum.okta.com/t/users-api-403-e0000005-response/16731/2 "2021-10-26T00:05:03Z")

</div>

Can you make sure you’re hitting the right endpoint when you make the call in Node?

Forewarning that I will chide you if this is not a server application and this /users call is being made on the front end.

---

<div class="post-metadata">

**Author:** ![sdunning](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/sdunning/32/2161_2.png) [@sdunning](https://devforum.okta.com/u/sdunning)\
**Post date:** [October 26, 2021, 12:59pm UTC](https://devforum.okta.com/t/users-api-403-e0000005-response/16731/3 "2021-10-26T12:59:32Z")

</div>

Almost that bad 😢 Typo in my code for building the Authorization header. Had `SWSS` instead of `SSWS`

---

<div class="post-metadata">

**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\
**Post date:** [October 26, 2021, 3:26pm UTC](https://devforum.okta.com/t/users-api-403-e0000005-response/16731/4 "2021-10-26T15:26:18Z")

</div>

oh no! Well at least you caught it fast

---

<div class="post-metadata">

**Author:** ![sdunning](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/sdunning/32/2161_2.png) [@sdunning](https://devforum.okta.com/u/sdunning)\
**Post date:** [October 26, 2021, 6:08pm UTC](https://devforum.okta.com/t/users-api-403-e0000005-response/16731/5 "2021-10-26T18:08:18Z")

</div>

Now I’m seeing the same response for lifecycle/activate

URL: https://${oktaDomain redacted}/api/v1/users/3443434343434/lifecycle/activate?sendEmail=false

I know for certain that it’s not the Authorization header because it’s using the same header being used for the base user API calls that work. Also, I can paste the same URL being used in the Node call into Postman and it works.

---

<div class="post-metadata">

**Author:** ![sdunning](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/sdunning/32/2161_2.png) [@sdunning](https://devforum.okta.com/u/sdunning)\
**Post date:** [October 26, 2021, 6:39pm UTC](https://devforum.okta.com/t/users-api-403-e0000005-response/16731/6 "2021-10-26T18:39:31Z")

</div>

Nevermind, another user error on my part with the httpclient post parameters.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/oktadev/original/1X/589c4c5f80de422d01f47cee7185a7fb8227835c.png) [@system](https://devforum.okta.com/u/system)\
**Post date:** [October 27, 2021, 6:39pm UTC](https://devforum.okta.com/t/users-api-403-e0000005-response/16731/7 "2021-10-27T18:39:50Z")

</div>

Closed on October 27, 2021, 6:39pm UTC

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
