# ESI 401 Error

**URL:** <https://forums.eveonline.com/t/esi-401-error/486123>\
**Category:** Third Party Developers\
**Tags:** esi\
**Created:** [May 13, 2025, 3:24pm UTC](https://forums.eveonline.com/t/esi-401-error/486123 "2025-05-13T15:24:42Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Natalie\_Doran](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/natalie_doran/32/429886_2.png) [@Natalie\_Doran](https://forums.eveonline.com/u/Natalie_Doran)\
**Post date:** [May 13, 2025, 3:24pm UTC](https://forums.eveonline.com/t/esi-401-error/486123/1 "2025-05-13T15:24:42Z")

</div>

I have an app that fetches characters assets using ESI. It was working for a long time but today I started getting HTTP 401 error for all requests that require ESI scopes. I thought maybe my tokens are not valid anymore and I re-authenticated the characters and I still get the same error. I think there is an issue with ESI.

---

<div class="post-metadata">

**Author:** ![Erik\_Kalkoken](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/erik_kalkoken/32/436631_2.png) [@Erik\_Kalkoken](https://forums.eveonline.com/u/Erik_Kalkoken)\
**Post date:** [May 13, 2025, 3:29pm UTC](https://forums.eveonline.com/t/esi-401-error/486123/2 "2025-05-13T15:29:41Z")

</div>

Hey! CCP turned off v1 SSO tokens today. So if your app is still using the old version, that might explain your issue. Note that the SSO server still returns v1 tokens, but ESI no longer accepts it.

For more details see this: [Removal of v1 authentication tokens](https://developers.eveonline.com/blog/removal-of-v1-authentication-tokens)

---

<div class="post-metadata">

**Author:** ![Diadem\_Katelo](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/diadem_katelo/32/460391_2.png) [@Diadem\_Katelo](https://forums.eveonline.com/u/Diadem_Katelo)\
**Post date:** [May 13, 2025, 5:29pm UTC](https://forums.eveonline.com/t/esi-401-error/486123/3 "2025-05-13T17:29:16Z")

</div>

I’m having the same problem. My authorized 3rd party app was also working for months before today. Right now I’m able to authenticate the characters, but any subsequent calls for wallet, etc fail with unauthorized. Confirmed in Postman and in my own scripts. Testing in ESI Swagger UI works though.

---

<div class="post-metadata">

**Author:** ![Inactive\_Seller](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/inactive_seller/32/519163_2.png) [@Inactive\_Seller](https://forums.eveonline.com/u/Inactive_Seller)\
**Post date:** [May 13, 2025, 5:52pm UTC](https://forums.eveonline.com/t/esi-401-error/486123/4 "2025-05-13T17:52:50Z")

</div>

Literally use GEMINI, the LLM/ ia of google and ask him to do the JWT validation routin. I was in a hurry and geot the code 99% functionl an adapt quicky to full fill my needes. anyqye they need what are the plans with esi.

---

<div class="post-metadata">

**Author:** ![Diadem\_Katelo](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/diadem_katelo/32/460391_2.png) [@Diadem\_Katelo](https://forums.eveonline.com/u/Diadem_Katelo)\
**Post date:** [May 13, 2025, 6:10pm UTC](https://forums.eveonline.com/t/esi-401-error/486123/5 "2025-05-13T18:10:47Z")

</div>

I wasn’t paying close enough attention to the upcoming changes.

Migrating to OAuth V2 was pretty simple:

Update your authentication and token refresh endpoints to:

/v2/oauth/authorize  
/v2/oauth/token

You might also need to include a new State parameter.

Some more documentation here: [Single Sign-On - EVE Developer Documentation](https://developers.eveonline.com/docs/services/sso/)

---

<div class="post-metadata">

**Author:** ![Tarax](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/tarax/32/420205_2.png) [@Tarax](https://forums.eveonline.com/u/Tarax)\
**Post date:** [May 14, 2025, 1:33pm UTC](https://forums.eveonline.com/t/esi-401-error/486123/6 "2025-05-14T13:33:56Z")

</div>

Updating should be easy:  
All I had to do was add “/v2” to both my authorization and request uri’s.  
Then I re-authorize to get my new token and it all worked.

[https://login.eveonline.com/oauth/](https://login.eveonline.com/oauth/)…  
to:  
[https://login.eveonline.com/v2/oauth/](https://login.eveonline.com/v2/oauth/)…

As for the “state” parameter, I left it like I had it, which was “evesso”.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/eveonline/original/3X/4/1/41ec4921cbaca7a6f9ea556e7cc20018461eae5e.png) [@system](https://forums.eveonline.com/u/system)\
**Post date:** [August 12, 2025, 1:34pm UTC](https://forums.eveonline.com/t/esi-401-error/486123/7 "2025-08-12T13:34:32Z")

</div>

Closed on August 12, 2025, 1:34pm UTC

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