Skip to main content

attribute_mismatch

401 Attribute mismatch

Unable to authenticate because attributes on request don’t match stored attributes.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "attribute_mismatch",
  "error_message": "Unable to authenticate because attributes on request don't match stored attributes.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#attribute_mismatch"
}

Need help?


cannot_update_trusted_metadata

401 Cannot update trusted metadata

Stytch SDKs cannot update trusted metadata with user-provided values. Trusted metadata can only be updated by direct API integrations. SDKs are only allowed to update untrusted_metadata. Visit our docs to learn more.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "cannot_update_trusted_metadata",
  "error_message": "Stytch SDKs cannot update trusted metadata with user-provided values. Trusted metadata can only be updated by direct API integrations. SDKs are only allowed to update untrusted_metadata. Visit our docs to learn more.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#cannot_update_trusted_metadata"
}

Need help?


cname_invalid_for_http_only_cookies

401 Cname invalid for http only cookies

You didn’t provide a valid CNAME with your HTTP-only cookies setting set to ‘ENFORCED’. Consider updating the HTTP-only cookies setting to ‘ENABLED’ or making a request via the project’s configured CNAME.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "cname_invalid_for_http_only_cookies",
  "error_message": "You didn't provide a valid CNAME with your HTTP-only cookies setting set to 'ENFORCED'. Consider updating the HTTP-only cookies setting to 'ENABLED' or making a request via the project's configured CNAME.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#cname_invalid_for_http_only_cookies"
}

Need help?


cname_required_for_http_only_cookies

401 Cname required for http only cookies

You may not make a request via the default API URL (‘api.stytch.com’ or ‘test.stytch.com’) with your HTTP-only cookies setting set to ‘ENFORCED’. Consider updating the HTTP-only cookies setting to ‘ENABLED’ or making a request via the project’s configured CNAME.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "cname_required_for_http_only_cookies",
  "error_message": "You may not make a request via the default API URL ('api.stytch.com' or 'test.stytch.com') with your HTTP-only cookies setting set to 'ENFORCED'. Consider updating the HTTP-only cookies setting to 'ENABLED' or making a request via the project's configured CNAME.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#cname_required_for_http_only_cookies"
}

Need help?


401 Connected app consent revoked

The Connected App’s permission has been revoked. Complete another authorization flow to re-enable access.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "connected_app_consent_revoked",
  "error_message": "The Connected App's permission has been revoked. Complete another authorization flow to re-enable access.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#connected_app_consent_revoked"
}

Need help?


connected_app_supplied_redirect_url_not_found_in_client

401 Connected app supplied redirect url not found in client

The redirect URL supplied in the request is not registered to the client.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "connected_app_supplied_redirect_url_not_found_in_client",
  "error_message": "The redirect URL supplied in the request is not registered to the client.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#connected_app_supplied_redirect_url_not_found_in_client"
}

Need help?


endpoint_not_authorized_for_sdk

401 Endpoint not authorized for sdk

The project owner hasn’t authorized the Stytch SDK to call endpoints for this product.

Common Causes

  • You haven’t yet configured your Stytch project to allow SDK access to this product.

Troubleshooting

  • Enable the product via the Frontend SDK page in the Stytch Dashboard.
  • Toggle on the corresponding Enabled methods in the Frontend SDK page.
  • If you’re using our WebAuthn product, you’ll also need to enable “Manage user data” via the Frontend SDK page.
{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "endpoint_not_authorized_for_sdk",
  "error_message": "The project owner has not authorized the SDK to call this endpoint. Please enable it in the dashboard to continue: https://stytch.com/dashboard/sdk-configuration.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#endpoint_not_authorized_for_sdk"
}

Need help?


enterprise_endpoint

401 Enterprise endpoint

Thanks for trying Stytch! We’re glad you’re excited to try our new products, but this one requires approval before using. Please reach out to support@stytch.com if you’re interested.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "enterprise_endpoint",
  "error_message": "Thanks for trying Stytch! We're glad you're excited to try our new products, but this one requires approval before using. Please reach out to support@stytch.com if you're interested.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#enterprise_endpoint"
}

Need help?


insufficient_factors

401 Insufficient factors

User must be logged in with multiple categories of factors to call this endpoint.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "insufficient_factors",
  "error_message": "User must be logged in with multiple categories of factors to call this endpoint.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#insufficient_factors"
}

Need help?


oauth_unverified_email

401 Oauth unverified email

The user has not verified their email with the OAuth provider. Please encourage them to verify their email address and try again.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "oauth_unverified_email",
  "error_message": "The user has not verified their email with the OAuth provider. Please encourage them to verify their email address and try again.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#oauth_unverified_email"
}

Need help?


oidc_response_unverified_email

401 Oidc response unverified email

The user has not verified their email with the external provider. Please encourage them to verify their email address and try again.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "oidc_response_unverified_email",
  "error_message": "The user has not verified their email with the external provider. Please encourage them to verify their email address and try again.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#oidc_response_unverified_email"
}

Need help?


session_too_old_to_reset_password

401 Session too old to reset password

The provided session cannot be used to reset a password. It does not have an authentication_factor that was authenticated within the last 5 minutes. Please prompt the user to authenticate again before retrying the endpoint.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "session_too_old_to_reset_password",
  "error_message": "The provided session cannot be used to reset a password. It does not have an authentication_factor that was authenticated within the last 5 minutes. Please prompt the user to authenticate again before retrying the endpoint.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#session_too_old_to_reset_password"
}

Need help?


stale_factors

401 Stale factors

In order to call this endpoint, the user should have authenticated within the last hour. Please reauthenticate and try again.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "stale_factors",
  "error_message": "In order to call this endpoint, the user should have authenticated within the last hour. Please reauthenticate and try again.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#stale_factors"
}

Need help?


twitter_401

401 Twitter 401

Twitter responded with a 401 Unauthorized error.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "twitter_401",
  "error_message": "Twitter responded with a 401 Unauthorized error.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#twitter_401"
}

Need help?


unable_to_auth_biometric_registration

401 Unable to auth biometric registration

Biometric registration could not be authenticated.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unable_to_auth_biometric_registration",
  "error_message": "Biometric registration could not be authenticated.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unable_to_auth_biometric_registration"
}

Need help?


unable_to_auth_impersonation_token

401 Unable to auth impersonation token

The impersonation token could not be authenticated.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unable_to_auth_impersonation_token",
  "error_message": "The impersonation token could not be authenticated.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unable_to_auth_impersonation_token"
}

Need help?


401 Unable to auth magic link

The magic link could not be authenticated because it was either used or expired.

Common Causes

  • A user clicks a magic link they already used before
  • A user waits too long to click a magic link that has expired

Troubleshooting

  • Send a new magic link to the user
{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unable_to_auth_magic_link",
  "error_message": "The magic link could not be authenticated because it was either already used or expired. Send another magic link to this user.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unable_to_auth_magic_link"
}

Need help?


unable_to_auth_otp_code

401 Unable to auth otp code

The passcode could not be authenticated because it was either already used or expired. Send another passcode to this user.

Common Causes

  • The user may have inadvertently entered the same OTP code twice; either re-using a code they already authenticated or an expired code.
  • If you wrapped the OTPAuthenticate call in a useEffect and you are using React 18 in StrictMode, you may be double calling the method. See here for more details.

Troubleshooting

  • Review your code, and network requests (if using a frontend SDK) to determine if multiple requests are being made.
  • Send a new code to the user.
{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unable_to_auth_otp_code",
  "error_message": "The passcode could not be authenticated because it was either already used or expired. Send another passcode to this user.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unable_to_auth_otp_code"
}

Need help?


unable_to_auth_password_reset_token

401 Unable to auth password reset token

The password reset token could not be authenticated, try sending another password reset email to the user.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unable_to_auth_password_reset_token",
  "error_message": "The password reset token could not be authenticated, try sending another password reset email to the user.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unable_to_auth_password_reset_token"
}

Need help?


unable_to_auth_webauthn_registration

401 Unable to auth webauthn registration

WebAuthn registration could not be authenticated.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unable_to_auth_webauthn_registration",
  "error_message": "WebAuthn registration could not be authenticated.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unable_to_auth_webauthn_registration"
}

Need help?


unable_to_authenticate_recovery_code

401 Unable to authenticate recovery code

Unable to authenticate recovery code.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unable_to_authenticate_recovery_code",
  "error_message": "Unable to authenticate recovery code.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unable_to_authenticate_recovery_code"
}

Need help?


unable_to_authenticate_totp

401 Unable to authenticate totp

Unable to authenticate TOTP.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unable_to_authenticate_totp",
  "error_message": "Unable to authenticate TOTP.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unable_to_authenticate_totp"
}

Need help?


unauthorized_action

401 Unauthorized action

Unauthorized action.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unauthorized_action",
  "error_message": "Unauthorized action.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unauthorized_action"
}

Need help?


unauthorized_billing_permissions

401 Unauthorized billing permissions

This action or feature is not supported by your billing tier. Please visit https://stytch.com/dashboard/settings/pricing-plans for more information.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unauthorized_billing_permissions",
  "error_message": "This action or feature is not supported by your billing tier. Please visit https://stytch.com/dashboard/settings/pricing-plans for more information.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unauthorized_billing_permissions"
}

Need help?


unauthorized_credentials

401 Unauthorized credentials

The provided credentials (project_id and secret) were invalid, an incorrect password was provided to an Authenticate Password request, or an invalid/expired session token was included in a request.

Common Causes

  • Working with multiple Stytch Projects can result in the project_id and secret getting mixed up.
  • Improper clearing of revoked session cookies

Troubleshooting

  • Compare the secret and project_id you are using the the values in the Stytch Dashboard.
  • Confirm that the password provided to our Authenticate Password endpoint was correct, or prompt the user to reset their password.
  • Confirm the secret and project_id are associated within the same project.
  • Generate a new secret for your project_id in the Stytch Dashboard.
  • Ensure that there are no expired/invalid session tokens being included in requests.
{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unauthorized_credentials",
  "error_message": "Unauthorized credentials.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unauthorized_credentials"
}

Need help?


unauthorized_credentials_homepage

401 Unauthorized credentials homepage

Thanks for trying Stytch! Replace the project ID and secret with your credentials from the developer dashboard to start adding users. To get started, sign up here: https://stytch.com/login

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unauthorized_credentials_homepage",
  "error_message": "Thanks for trying Stytch! Replace the project ID and secret with your credentials from the developer dashboard to start adding users. To get started, sign up here: https://stytch.com/login",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unauthorized_credentials_homepage"
}

Need help?


unauthorized_project_id_live

401 Unauthorized project id live

Unauthorized credentials. Looks like the project ID supplied in the request was a live project id. Try using a test project id when hitting test.stytch.com.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unauthorized_project_id_live",
  "error_message": "Unauthorized credentials. Looks like the project ID supplied in the request was a live project id. Try using a test project id when hitting test.stytch.com.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unauthorized_project_id_live"
}

Need help?


unauthorized_project_id_test

401 Unauthorized project id test

Unauthorized credentials. Looks like the project ID supplied in the request was a test project id. Try using a live project id when hitting stytch.com.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unauthorized_project_id_test",
  "error_message": "Unauthorized credentials. Looks like the project ID supplied in the request was a test project id. Try using a live project id when hitting stytch.com.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unauthorized_project_id_test"
}

Need help?


unavailable_endpoint

401 Unavailable endpoint

Thanks for trying Stytch! We’re glad you’re excited to try our new products, but this one is still under construction. Please reach out to support@stytch.com if you’re interested.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "unavailable_endpoint",
  "error_message": "Thanks for trying Stytch! We're glad you're excited to try our new products, but this one is still under construction. Please reach out to support@stytch.com if you're interested.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#unavailable_endpoint"
}

Need help?


user_unauthenticated

401 User unauthenticated

User must have an active Stytch session to call this method. Have you logged in yet?

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "user_unauthenticated",
  "error_message": "User must have an active Stytch session to call this method. Have you logged in yet?",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#user_unauthenticated"
}

Need help?


weak_factor_combination

401 Weak factor combination

This session does not contain a strong combination of factors.

{
  "status_code": 401,
  "request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
  "error_type": "weak_factor_combination",
  "error_message": "This session does not contain a strong combination of factors.",
  "error_url": "https://stytch.com/docs/api-reference/consumer/api/errors/401#weak_factor_combination"
}

Need help?