When will this feature be available?
The Auth API enhanced SMS text will be rolled out on June 10th.
What is this feature about?
We are excited to announce an upcoming enhancement to our SMS text customization feature, designed to provide even more flexibility and control over the SMS text.
The current usage of the
sms_text attribute allows setting the SMS text that precedes the generated OTP. With this upcoming feature, it will be possible to provide a customized SMS text template that includes the
$OTP variable, that is automatically replaced with the user's One-Time Password (OTP), before sending the SMS to the recipient. This empowers the full customization of the SMS text
How to use this feature?
To take advantage of this enhanced functionality, simply update the value provided in the
sms_text attribute of the SMS Device Activation or Authenticate with SMS endpoints, with an SMS text template that includes the
In case that an
sms_text is provided without having the
$OTP variable, the generated OTP will be inserted at the end of the SMS text.
With this improvement, the
sms_text attribute will support new line escape sequences. Please find the below usage example:
”sms_text”: “Your login code is $OTP.\nDo not share it with anyone”
Does this change have any impact on my Futurae API integration?
This change has no impact on existing Futurae API integrations as the current usage of
sms_text (i.e., without the use of the
$OTP variable) is still supported, therefore no change is required.
For any questions please contact our support at firstname.lastname@example.org.