"HTTP 401 Okta E0000011 Invalid Token provided" Error When Calling APIs
Last Updated:
Overview
API calls fail with the following error when the API token is no longer valid because the account that created it is inactive.
HTTP 401 Okta E0000011 Invalid Token provided
After reactivating the account that created the API token, API calls succeed again.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Application Programming Interface (API) tokens
Cause
The account that created the API token is inactive, so Okta rejects API calls that use that token and returns the invalid token error.
Solution
How is the invalid API token error resolved?
Identify the account that created the API token and reactivate that account to restore API access.
- In the Okta Admin Console, go to Security > API.
- Select the Tokens tab.
- Identify the creator's username under the API token name.
- In the Okta Admin Console, go to Directory > People.
- Select the deactivated or suspended user.
- Select Activate on the user's profile page.
How is API access restored if the creator account cannot be reactivated?
Create a new API token from a different active account to restore API access.
How are invalid API tokens prevented in Okta?
Create API tokens by using a service account instead of an individual administrator account to prevent token invalidation when an individual account becomes suspended or deleted.
NOTE: Create API tokens using a service account instead of an individual administrator's account. This prevents API tokens from becoming invalid if the individual's account is suspended or deleted.
