Active with remarks |
---|
This application needs additional settings. Please follow the documentation below to create your connection. |
The Twilio Verify modules enable you to, create, update, list, retrieve, and delete the verification services and verifications in your Twilio Verify account.
Prerequisites
-
A Twilio Verify account – create an account at twilio.com/verify.
The module dialog fields that are displayed in bold (in the Boost.space Integrator scenario, not in this documentation article) are mandatory!
To connect your Twilio Verify account to Boost.space Integrator you need to obtain the API token from your Twilio Verify account and insert it in the Create a connection dialog in the Boost.space Integrator module.
-
Log in to your Twilio Verify account.
-
Copy the Account SID and API Token to a safe place.
-
Go to Boost.space Integrator and open the Twilio Verify module’s Create a connection dialog.
-
In the Connection name field, enter a name for the connection.
-
In the Account SID and API Token fields, enter the account SID and token details copied in step 3 and click Continue.
The connection has been established.
Fetches all of the verification services.
|
|
|
Select or map the account SID of the verification service to fetch the resource from. |
|
Enter (map) the Twilio provided string that uniquely identifies the verification resource to fetch. |
Retrieves an existing verification service.
|
|
|
Select or map the Twilio provided string that uniquely identifies the verification service resource to fetch. |
Creates a new verification service.
|
|
|
Enter (map) a name for the verification service. For example, |
|
Enter (map) the length of the verification code to generate. You can enter an integer between 4 and 10, inclusive. |
|
Select whether to perform a lookup with each verification started and return info about the phone number. |
|
Select whether to ask the user to press a number before delivering the verification code in a phone call. |
|
Enter (map) the name of an alternative text-to-speech service to use in phone calls. This field applies only to TTS languages. |
|
Select whether to pass the PSD2 transaction parameters when starting a verification. |
|
Enter (map) the Mailer SID associated with the verify service. this information is used for creating verifications through the email channel. |
|
Select whether to add a security warning at the end of an SMS verification body. By default, this option is disabled and applies only to SMS. For example, a sample message looks like this: |
|
Select whether to allow sending verifications with a custom code instead of a randomly generated one. This option is not available to all users. Please contact your account agent. |
|
Add the push details:
Enter (map) the date on which you want to push the code. Optional configuration for the Push factors.If true, includes the date in the Challenge’s response.Otherwise, the date is omitted from the response.For more information, see the Challenge resource’s details parameter.
Enter (map) the APN Credential for this service. This information allows sending push notifications to iOS devices. For more information, see the Credential Resource.
Enter (map) the FCM Credential for this service. This information allows sending push notifications to Android devices. |
Updates an existing verification service.
|
|
|
Select or map the Verification Service SID whose details you want to update. |
|
Enter (map) a name for the verification service. For example, |
|
Enter (map) the length of the verification code to generate. You can enter an integer between 4 and 10, inclusive. |
|
Select whether to perform a lookup with each verification started and return info about the phone number. |
|
Select whether to ask the user to press a number before delivering the verification code in a phone call. |
|
Enter (map) the name of an alternative text-to-speech service to use in phone calls. This field applies only to TTS languages. |
|
Select whether to pass the PSD2 transaction parameters when starting a verification. |
|
Enter (map) the Mailer SID associated with the verify service. this information is used for creating verifications through the email channel. |
|
Select whether to add a security warning at the end of an SMS verification body. By default, this option is disabled and applies only to SMS. For example, a sample message looks like this: |
|
Select whether to allow sending verifications with a custom code instead of a randomly generated one. This option is not available to all users. Please contact your account agent. |
|
Add the push details:
Enter (map) the date on which you want to push the code. Optional configuration for the Push factors.If true, includes the date in the Challenge’s response.Otherwise, the date is omitted from the response.For more information, see the Challenge resource’s details parameter.
Enter (map) the APN Credential for this service. This information allows sending push notifications to iOS devices. For more information, see the Credential Resource.
Enter (map) the FCM Credential for this service. This information allows sending push notifications to Android devices. |
Deletes an existing verification service.
|
Select or map the Twilio provided string that uniquely identifies the verification service resource you want to delete. |
Retrieves an existing verification.
|
|
|
Select or map the Verification Service SID whose details you want to retrieve. |
|
Enter (map) the Twilio provided string that uniquely identifies the verification resource to fetch. |
Starts a new verification.
|
|
|
Enter (map) the phone number or email to verify. The phone numbers must be in E.164 format. |
|
Select or map a method to verify:
|
|
Add the channel configurations: FromEnter (map) the phone number. This field is required if submitting the From NameEnter (map) the name from which you want to configure the channel. This field is required if submitting the Template IDEnter (map) the Template ID. This information overrides the default template from the Verify Service email integration. To create a new template in the SendGrid dashboard, see the SendGrid docs. SubstitutionsEnter (map) key-value pair variable substitution for dynamic email templates. |
|
Enter (map) the SID of the verification service under which you want to create the resource. |
|
Add the custom key-value pairs of programmable rate limits. The associated value pairs represent values in the request that you are rate-limiting on. You may include multiple rate limit values in each request. |
|
Enter (map) the custom user-defined friendly name that overwrites the existing one in the verification message. |
|
Enter (map) the text of a custom message to use for the verification. |
|
Enter (map) a pre-generated code to use for verification. Enter a value between 4 and 10 characters long. |
|
Enter (map) the amount of the associated PSD2 compliant transaction. This option requires enabling the PSD2 Service flag. |
|
Enter (map) the payee of the associated PSD2 compliant transaction. This option requires enabling the PSD2 Service flag enabled. |
Updates a verification status.
|
|
|
Select or map the SID of the verification service to fetch the resource whose verification status you want to update. |
|
Enter (map) the verification SID. |
|
Select or map the status of the verification:
|
Checks a verification.
|
|
|
Select or map the SID of the verification service to fetch t |
|
Enter (map) a pre-generated code to use for verification. Enter a value between 4 and 10 characters long. |
|
Enter (map) the phone number or email to verify. The phone numbers must be in E.164 format. |
|
Enter (map) the verification SID that uniquely identifies the verification code. . Either this parameter or the phone number/email must be specified. |
|
Enter (map) the amount of the associated PSD2 compliant transaction. This option requires enabling the PSD2 Service flag. |
|
Enter (map) the payee of the associated PSD2 compliant transaction. This option requires enabling the PSD2 Service flag enabled. |
Performs an arbitrary authorized API call.
|
||||
|
Enter a path relative to
|
|||
|
Select the HTTP method you want to use:
to retrieve information for an entry.
to create a new entry.
to update/replace an existing entry.
to make a partial entry update.
to delete an entry. |
|||
|
Enter the desired request headers. You don’t have to add authorization headers; we already did that for you. |
|||
|
Enter the request query string. |
|||
|
Enter the body content for your API call. |
Do you need help with something specific regarding Twilio Verify?
We are here for you.
Get support on the road to success from real experts.
We will help you set up your business processes, create connections from your current IT stack, and set up data analysis.
Get in touch