Challenge Resource
The Challenge resource is currently used by Verify Push and Verify TOTP features. It represents a single verification attempt of an Entity using a Factor. When the factor_type is push, a Challenge is created to verify the signature of the message sent from the registered device with the public key stored in the Factor. When the factor_type is totp, a Challenge is created to verify that the TOTP code provided by the user matches the one generated by the seed stored in the Factor. Some Challenge properties apply to all factor_types and others do not. A single Entity links to multiple Factors and a single Factor links to multiple Challenges.
Verify TOTP is currently in the Pilot maturity stage, which means that you need to contact sales to request that your Twilio account gets access to it. The Challenge will not work for Verify TOTP without this access.
Verify Push is priced per approved/denied Challenge
料金表Consistent with overall Verify pricing, Verify Push will be billed at a rate of $0.05 per verification. In technical terms, a "verification" is defined as a Challenge that is updated with a status of approved or denied.
Usage of Verify TOTP, as measured by the creation/updating of Challenges of factor_type:totp, is free while it's in the Pilot maturity stage. Billing will start once Verify TOTP reaches Private/Public Beta maturity stage, and pricing details will be provided then.
Challenge properties
| Resource Properties in REST API format | |
|---|---|
sid
|
A 34 character string that uniquely identifies this Challenge. |
account_sid
|
The unique SID identifier of the Account. |
service_sid
|
The unique SID identifier of the Service. |
entity_sid
|
The unique SID identifier of the Entity. |
identity
|
Customer unique identity for the Entity owner of the Challenge. This value must be between 8 and 64 characters long. |
factor_sid
|
The unique SID identifier of the Factor. |
date_created
|
The date that this Challenge was created, given in ISO 8601 format. |
date_updated
|
The date that this Challenge was updated, given in ISO 8601 format. |
date_responded
|
The date that this Challenge was responded, given in ISO 8601 format. |
expiration_date
|
The date-time when this Challenge expires, given in ISO 8601 format. The default value is five (5) minutes after Challenge creation. The max value is sixty (60) minutes after creation. |
status
|
The Status of this Challenge. One of |
responded_reason
|
Reason for the Challenge to be in certain |
details
|
Details provided to give context about the Challenge. Intended to be shown to the end user. |
hidden_details
|
Details provided to give context about the Challenge. Not intended to be shown to the end user. It must be a stringified JSON with only strings values eg. |
factor_type
|
The Factor Type of this Challenge. Currently |
url
|
The URL of this resource. |
links
|
Contains a dictionary of URL links to nested resources of this Challenge. |
Create a Challenge resource
https://verify.twilio.com/v2/Services/{ServiceSid}/Entities/{Identity}/Challenges
パラメーター
| Parameters in REST API format | |
|---|---|
service_sid
Path
|
The unique SID identifier of the Service. |
identity
Path
|
The unique external identifier for the Entity of the Service. This identifier should be immutable, not PII, and generated by your external system, such as your user's UUID, GUID, or SID. This value must be between 8 and 64 characters long. |
factor_sid
必須
|
The unique SID identifier of the Factor. |
expiration_date
オプション
|
The date-time when this Challenge expires, given in ISO 8601 format. The default value is five (5) minutes after Challenge creation. The max value is sixty (60) minutes after creation. |
details.message
オプション
|
Shown to the user when the push notification arrives. Required when |
details.fields
オプション
|
A list of objects that describe the Fields included in the Challenge. Each object contains the label and value of the field, the label can be up to 36 characters in length and the value can be up to 128 characters in length. Used when |
hidden_details
オプション
|
Details provided to give context about the Challenge. Not shown to the end user. It must be a stringified JSON with only strings values eg. |
auth_payload
オプション
|
Optional payload used to verify the Challenge upon creation. Only used with a Factor of type |
例 1
例 2
Fetch a Challenge resource
https://verify.twilio.com/v2/Services/{ServiceSid}/Entities/{Identity}/Challenges/{Sid}
パラメーター
| Parameters in REST API format | |
|---|---|
service_sid
Path
|
The unique SID identifier of the Service. |
identity
Path
|
The unique external identifier for the Entity of the Service. This identifier should be immutable, not PII, and generated by your external system, such as your user's UUID, GUID, or SID. This value must be between 8 and 64 characters long. |
sid
Path
|
A 34 character string that uniquely identifies this Challenge. |
例 1
Read multiple Challenge resources
https://verify.twilio.com/v2/Services/{ServiceSid}/Entities/{Identity}/Challenges
パラメーター
| Parameters in REST API format | |
|---|---|
service_sid
Path
|
The unique SID identifier of the Service. |
identity
Path
|
Customer unique identity for the Entity owner of the Challenge. This value must be between 8 and 64 characters long. |
factor_sid
オプション
|
The unique SID identifier of the Factor. |
status
オプション
|
The Status of the Challenges to fetch. One of |
例 1
Update a Challenge resource
https://verify.twilio.com/v2/Services/{ServiceSid}/Entities/{Identity}/Challenges/{Sid}
パラメーター
| Parameters in REST API format | |
|---|---|
service_sid
Path
|
The unique SID identifier of the Service. |
identity
Path
|
Customer unique identity for the Entity owner of the Challenge. This value must be between 8 and 64 characters long. |
sid
Path
|
A 34 character string that uniquely identifies this Challenge. |
auth_payload
オプション
|
The optional payload needed to verify the Challenge. E.g., a TOTP would use the numeric code. For |
例 1
ヘルプが必要ですか？
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Community Forums or browsing the Twilio tag on Stack Overflow.