Okta API Returns a 403 Error E0000097 When Listing User Factors - "There is no verified phone number on file"
Last Updated:
Overview
A hanging phone enrollment in a pending verification state causes a 403 error when listing user factors via the Okta API. Contact Okta Support to enable a specific feature flag to resolve this issue. When calling the Okta API to list user factors, Okta generates a 403 error stating there is no verified phone number on file.
GET /api/v1/users/<userId>/factors
Status: 403 error
Error:
{
"errorCode": "E0000097",
"errorSummary": "There is no verified phone number on file.",
"errorLink": "E0000097",
"errorId": "<errorId>",
"errorCauses": []
}
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta API
- Factors API
Cause
A hanging phone enrollment that remains in a pending verification state causes this error. The backend displays the factor, but the Admin Console and standard API calls do not show it. This discrepancy causes Okta to generate a 403 error when an administrator attempts to list, manage, or reset factors for the user.
Solution
How is the 403 error resolved?
Open a case with Okta Support to enable the required feature flag and delete the hanging factor.
- Open a case with Okta Support.
- Request Okta Support to enable the required feature flag for the Okta org.
- After the FF is enabled, admins should be able to run the factors API without receiving the error
