---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/60436#article
headline: "60436: Recipient invalid or not provided"
url: https://www.twilio.com/docs/api/errors/60436
inLanguage: en
dateModified: 2026-06-08T12:04:59.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 60436: Recipient invalid or not provided

Log Type: APPLICATION

Log Level: ERROR

## Description

Twilio returns this error when your Verify request does not include a valid recipient destination. Verify accepts a phone number or an email address as the destination, and phone numbers must be provided in `E.164` format.

### Possible causes

* The request did not include the recipient destination required for the verification request.
* The recipient is a phone number that is not formatted in `E.164`.
* The selected Verify channel and recipient type do not match, such as using the `email` channel without an email address.
* Your application passed unconfirmed user input, such as a mistyped phone number or email address. Confirming contact information and validating phone numbers before sending an OTP helps catch these errors earlier.

### Possible solutions

* Include the recipient destination in the request body and resend the verification request.
* For `sms`, `call`, `whatsapp`, `sna`, or `auto`, send the recipient as a complete `E.164` phone number, such as `+14155552671`.
* For the `email` channel, send an email address as the destination and make sure your Verify email integration is configured before sending email verifications.
* Normalize and validate phone numbers before creating a verification. Use Lookup if you need help converting or screening user input before you send the OTP.

#### Additional resources

* [Start a verification](/docs/verify/api/verification)
* [Send Email Verifications with Verify and Twilio SendGrid](/docs/verify/email)
* [Lookup](/docs/lookup)