---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/60370#article
headline: "60370: Factor config invalid or not provided"
url: https://www.twilio.com/docs/api/errors/60370
inLanguage: en
dateModified: 2026-06-08T11:38:30.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 60370: Factor config invalid or not provided

Log Type: APPLICATION

Log Level: ERROR

## Description

This error occurs when your Verify Factor request does not include a valid `config` value for the selected `factorType`. Send the `config` fields that match the factor you are creating or updating. For Push factors, Verify expects required configuration fields such as `config.appId`, `config.notificationPlatform`, `config.notificationToken`, and `config.sdkVersion`. For TOTP factors, any `config` values you send must stay within the documented ranges. For Passkeys factors, send a valid passkey configuration object.

### Possible causes

* The request did not include a `config` value for a Factor request that requires it.
* The `config` fields do not match the selected `factorType`.
* A Push factor request is missing one or more required fields such as `config.appId`, `config.notificationPlatform`, `config.notificationToken`, or `config.sdkVersion`.
* A Push factor request includes an invalid `config.notificationPlatform` value or a `config.notificationToken` that is shorter than 32 characters or longer than 255 characters.
* A TOTP factor request includes an out-of-range value for `config.timeStep`, `config.skew`, or `config.codeLength`.
* A TOTP factor request includes an unsupported `config.alg` value.
* A Passkeys factor request includes an invalid or incomplete passkey configuration, such as missing or invalid relying party settings or unsupported authenticator preference values.

### Possible solutions

* Review the request for your selected `factorType` and send only the supported `config` fields for that factor.
* For Push factors, include valid values for `config.appId`, `config.notificationPlatform`, `config.notificationToken`, and `config.sdkVersion`.
* For Push factors, use one of the supported notification platform values and verify that `config.notificationToken` is between 32 and 255 characters long.
* For TOTP factors, keep `config.timeStep` between 20 and 60, `config.skew` between 0 and 2, and `config.codeLength` between 3 and 8.
* For TOTP factors, use a supported `config.alg` value such as `sha1`, `sha256`, or `sha512`.
* For Passkeys factors, send a valid passkey `config` object with supported relying party and authenticator settings.
* Compare your request with the Verify API examples and confirm that your parameter names and structure match the documented request format.

#### Additional resources

* [Factor Resource](/docs/verify/api/factor)
* [Passkeys Factor Resource](/docs/verify/api/passkeys-factor)
* [Verify TOTP Overview](/docs/verify/totp)