---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/60404#article
headline: "60404: Input Error"
url: https://www.twilio.com/docs/api/errors/60404
inLanguage: en
dateModified: 2026-06-09T11:00:42.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 60404: Input Error

Log Type: APPLICATION

Log Level: ERROR

## Description

Verify returns this error when it cannot process one or more request inputs. This usually means the request is missing a required field, includes a malformed value, or sends a parameter that does not match the Verify endpoint or channel you are using.

### Possible causes

* The request is missing a required parameter. For example, creating a verification requires `serviceSid`, `to`, and `channel`. Checking a verification requires `serviceSid` and either `to` or `verificationSid`.
* The `to` value is not formatted correctly for the selected channel. Phone numbers sent to Verify must be in `E.164` format.
* The request includes an unsupported or mismatched channel configuration, such as an invalid `channel` value or a `TemplateSid` on a channel other than SMS or Voice.
* A structured field is malformed, such as `serviceSid`, `verificationSid`, `TemplateSid`, or `deviceIp`. Verify expects specific SID prefixes and lengths, and `deviceIp` must be a valid IPv4 or IPv6 address if you provide it.
* A code or channel-specific value does not meet parameter requirements, such as a `customCode` or verification `code` that is not between 4 and 10 characters, or an email sender override in `channelConfiguration` that is not a valid email address.

### Possible solutions

* Validate the request before you send it. Make sure you are using the correct Verify endpoint and including every required field for that endpoint.
* Normalize phone numbers to `E.164` before sending them to Verify. This helps prevent formatting errors in the `to` parameter.
* Use only supported Verify channel values. If you pass channel-specific parameters, confirm they are valid for that channel. For example, use `TemplateSid` only with SMS or Voice.
* Validate SID and structured parameter formats in your application before making the API request. Confirm that `serviceSid` starts with `VA`, `verificationSid` starts with `VE`, and `TemplateSid` starts with `HJ`.
* If you use Verify email, confirm your email integration is set up correctly and that any `channelConfiguration.from` override contains a valid email address.
* Review Verify Logs in Console to identify which field failed validation, then correct the request and retry.

#### Additional resources

* [Start a Verification](/docs/verify/api/verification)
* [Check a Verification](/docs/verify/api/verification-check)
* [What is E.164?](/docs/glossary/what-e164)