TODO: Resource-level docs
Verify a specific Challenge.
Path parameters
-
The unique SID identifier of the Service.
Minimum length is
34, maximum length is34. Format should match the following pattern:^VA[0-9a-fA-F]{32}$. -
Customer unique identity for the Entity owner of the Challenge. This identifier should be immutable, not PII, length between 8 and 64 characters, and generated by your external system, such as your user's UUID, GUID, or SID. It can only contain dash (-) separated alphanumeric characters.
-
A 34 character string that uniquely identifies this Challenge.
Minimum length is
34, maximum length is34. Format should match the following pattern:^YC[0-9a-fA-F]{32}$.
Body
-
The optional payload needed to verify the Challenge. E.g., a TOTP would use the numeric code. For
TOTPthis value must be between 3 and 8 characters long. ForPushthis value can be up to 5456 characters in length -
Custom metadata associated with the challenge. This is added by the Device/SDK directly to allow for the inclusion of device information. It must be a stringified JSON with only strings values eg.
{"os": "Android"}. Can be up to 1024 characters in length.
curl \
--request POST 'https://verify.twilio.com/v2/Services/{ServiceSid}/Entities/{Identity}/Challenges/{Sid}' \
--user "username:password" \
--header "Content-Type: application/x-www-form-urlencoded" \
--data 'AuthPayload=string'
{
"account_sid": "string",
"date_created": "2026-05-04T09:42:00Z",
"date_responded": "2026-05-04T09:42:00Z",
"date_updated": "2026-05-04T09:42:00Z",
"entity_sid": "string",
"expiration_date": "2026-05-04T09:42:00Z",
"factor_sid": "string",
"factor_type": "push",
"identity": "string",
"links": {},
"responded_reason": "none",
"service_sid": "string",
"sid": "string",
"status": "pending",
"url": "https://example.com"
}