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

# 60366: Entity invalid or not provided

Log Type: APPLICATION

Log Level: ERROR

## Description

Twilio returns this error when your Verify request does not include a valid Entity identifier. In Verify, an Entity represents the user or identity being verified, and the required identifier must be provided in the format expected by the endpoint.

### Possible causes

* The request did not include `Identity` where the Verify endpoint requires it.
* The `Identity` value is not valid for Verify. It must be 8 to 64 characters long and can contain only dash-separated alphanumeric characters.
* The request used an `Identity` value that does not match the Entity for the Verify Service.
* The request to an Entity, Factor, or Challenge endpoint omitted the required `{Identity}` path parameter.

### Possible solutions

* Add the required `Identity` value to the request. When you create an Entity, send `Identity` in the request body.
* For Entity, Factor, and Challenge endpoints, include the correct `{Identity}` value in the request path.
* Validate the Entity identifier before you send the request. Use an immutable identifier generated by your system, such as a UUID, GUID, or SID.
* Make sure the identifier is 8 to 64 characters long and contains only dash-separated alphanumeric characters.
* Reuse the same Entity identity for related Verify resources in the same Service.

#### Additional resources

* [Entity Resource](/docs/verify/api/entity)
* [Factor Resource](/docs/verify/api/factor)
* [Challenge Resource](/docs/verify/api/challenge)