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

# 68004: Input Error

Log Type: APPLICATION

Log Level: ERROR

## Description

You may see this error when Verify rejects malformed or incomplete input while starting a verification or submitting a verification check. Review the parameters you send and confirm they match the required formats, required fields, and SID patterns for the Verify endpoint you are calling.

### Possible causes

* The `to` value is missing, or the destination phone number is not in `E.164` format when you start or check a phone verification.
* The `channel` value is missing or not one of the supported Verify channels for starting a verification, such as `sms`, `call`, `whatsapp`, `email`, `sna`, or `auto`.
* The request uses an invalid `serviceSid` value that does not match the required `VA` SID format.
* A verification check request does not include either `to` or `verificationSid`, or the `verificationSid` value does not match the required `VE` SID format.
* A code-based request sends a `code` or `customCode` value outside Verify's supported 4 to 10 character range.
* An SNA verification check omits `snaClientToken` or sends a value that does not match the token returned by the SNA URL invocation.

### Possible solutions

* Send the request in `application/x-www-form-urlencoded` format and include all required parameters for the endpoint you are using. A new verification requires `to` and `channel`. A verification check requires either `to` or `verificationSid`.
* Format destination phone numbers in `E.164`, for example `+14155552671`, before sending the request.
* Validate `serviceSid` and `verificationSid` before you submit the request. Verify Service SIDs start with `VA`. Verification SIDs start with `VE`.
* If you start a verification, use only a supported `channel` value for Verify.
* If you use `customCode` or submit a `code` in a verification check, keep the value between 4 and 10 characters.
* If you use Silent Network Auth, pass the `snaClientToken` from the SNA URL invocation into the verification check request.

#### 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)