Create an OTP template
Create an OTP template. Only name is required, every other field falls back to your account default. A create is refused once your account holds 500 templates.
In order to get access to this endpoint, contact our support team.
name is required: every other field falls back to your account default, so you can create a template per sub-customer with nothing but a name and a suffix. A create is refused once your account holds 500 templates.
Custom suffixes are checked before they are stored. Sending a suffix while custom suffixes are not enabled on your account is refused with custom_suffix_not_enabled. A suffix that is malformed is refused with invalid_suffix, one that reads like another company or a public institution with suffix_not_allowed, and one written in an alphabet we do not support yet with suffix_script_not_supported.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
The name of the template.
"Acme Bank"
The kind of message the template sends. Defaults to optimized.
optimized, psd2, account-takeover The custom text appended to the message. Requires custom suffixes to be enabled on your account.
"AcmeBank"
The number of digits in the verification code, between 4 and 8.
6
How many minutes a code stays valid after it was sent, between 1 and 1440.
10
How many times the end user may ask for the code to be sent again, between 1 and 50.
3
How many seconds the end user must wait between two of those manual retries, between 1 and 3600.
30
How many verifications one phone number may run over sliding_window_hours, between 1 and 1000.
5
The number of hours the per_phone_number_limit rate limit is measured over, between 1 and 72.
24
The security wording appended to the message.
none, basic, expiration, anti_phishing How many times Prelude resends the code on its own, between 1 and 5.
1
Whether requesting a new code invalidates the codes sent before it.
true
Response
Created
The identifier of the template, to pass as template_id when creating a verification.
"template_01k8ap1btqf5r9fq2c8ax5fhc9"
The name of the template.
"Acme Bank"
The kind of message the template sends. Possible values are:
optimized- A standard OTP message.psd2- A PSD2 strong customer authentication message.account-takeover- An account takeover confirmation message.
optimized, psd2, account-takeover The number of digits in the verification code.
6
How many minutes a code stays valid after it was sent.
10
How many times the end user may ask for the code to be sent again.
3
How many seconds the end user must wait between two of those manual retries.
30
How many verifications one phone number may run over sliding_window_hours.
5
The number of hours the per_phone_number_limit rate limit is measured over.
24
The security wording appended to the message. Possible values are:
none- No security wording.basic- A short do-not-share warning.expiration- The basic warning plus the code expiration.anti_phishing- The strongest anti-phishing wording.
none, basic, expiration, anti_phishing How many times Prelude resends the code on its own, without the end user asking.
1
Whether requesting a new code invalidates the codes sent before it, so only the most recently sent code is valid.
true
The custom text appended to the message. Absent when the template appends none.
"AcmeBank"
The date and time when the template was created. Absent on templates created before this was recorded.
"2024-01-01T12:00:00Z"