Your client side application uses the AccessToken
resource to authenticate its request to the Verify Push API when creating (i.e., enrolling or registering) an Entity and/or Factor.
While this Verify Push AccessToken
resource is similar to those used by Twilio voice/chat/video products, it cannot be reused between them.
The Type of the Factor. Currently only push
is supported.
push
A human readable description of this factor, up to 64 characters. For a push factor, this can be the device's name.
The access token generated for enrollment, this is an encrypted json web token.
POST https://verify.twilio.com/v2/Services/{ServiceSid}/AccessTokens
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.
The friendly name of the factor that is going to be created with this access token
How long, in seconds, the access token is valid. Can be an integer between 60 and 300. Default is 60.
GET https://verify.twilio.com/v2/Services/{ServiceSid}/AccessTokens/{Sid}
A 34 character string that uniquely identifies this Access Token.