Who is affected: Customers using the Telesign Full-service Java SDK Products affected: Telesign Full-service Java SDK
Changes
The Telesign Full-service Java SDK now supports Messaging and the Verify API: The addition of Messaging and Verify API to the Telesign Full-service Java SDK provides support for additional communication channels, including Rich Communication Services (RCS), WhatsApp, Viber, MMS, SMS, and email.
How this may affect you
Send messages to additional channels: You can send messages on your users’ channels of choice using Messaging.
Send one-time passcodes (OTPs) to additional channels: You can send OTPs on your users’ channels of choice using the Verify API.
Maintaining compatibility: This change does not impact the use of other APIs through the Telesign Full-service Java SDK.
Additional information
Go to our developer documentation for Messaging and Verify API for more information.
If you would like to enable Telesign Messaging or the Verify API for your account, please contact us.
Who is affected: Customers using Messaging Products affected: Messaging
Changes
Get transaction status added to Messaging: You can use get transaction status for all of your Messaging transactions to retrieve the final status of a transaction. See Get transaction status for more information about using this feature.
Availability of get transaction status: You can use get transaction status to retrieve the status of a transaction for up to 12 hours after you send a request.
Auto-generated OTP code feature added: The auto-generated OTP feature for Messaging allows you to have multiple use cases (including OTP), with only one integration point. You can extend the use cases by defining different templates in your request. To learn more about using auto-generated OTP codes and get transaction status, see Messaging - Get transaction status after auto-generating an OTP code.
Channels supporting auto-generated OTP codes: WhatsApp, Viber, RCS, SMS, and email support auto-generated OTP codes. The same OTP code is used by all channels so that the fallback channels can continue the verification process when needed.
How this may affect you
Expanded choices for obtaining delivery status: The addition of Get transaction status to Messaging means that you now have a choice of two methods for obtaining final delivery status for Messaging transactions.
Auto-generated OTP codes simplify integrations:Your integrations can be simpler using the auto-generated OTP feature because you only need to have one integration point. Likewise, because the OTP code generation is Telesign's responsibility, you do not need generate your own code when using this feature.
Additional information
Go to our developer documentation for Messaging for more information about Messaging. If you are new to Telesign or have questions regarding Telesign's Messaging product, please contact us.
Who is affected: Customers using Messaging Products affected: Messaging (Viber)
Changes
Viber verification messages added: Viber now supports verification messages, a new message type designed for sending one-time passwords (OTP) using Viber's pre-designed and pre-approved template. Learn more about how to send Viber verification messages.
Localization supported: Viber verification messages can be sent in one of 33 languages which can be selected when sending the message.
Fallback channels supported: To ensure that your verification messages reach end users that may not have Viber, Messaging provides the option to specify fallback channels when using Viber verification messages.
Transaction Callback Service supported: Use Transaction Callback Service with Viber verification messages to receive delivery status updates for your requests.
Get transaction status supported: You can also use Get transaction status to get the delivery status and other details for your Viber verification transactions.
How this may affect you
Potential for reduced costs: By sending messages using this type of transaction, you could get the lowest rate for domestic traffic compared to SMS and other Viber business message types.
Additional information
Go to our developer documentation for Messaging for more information about Messaging. If you are new to Telesign or have questions regarding Telesign's Messaging product, please contact us.
Who is affected: Customers using Intelligence Products affected: Intelligence
Changes
Parameter is ignored in POST requests: The request_risk_insights parameter, previously required for Intelligence, is now deprecated and will be ignored in the POST requests. It will behave as if the request_risk_insights parameter is always set to true.
Parameter is removed from the response: The request_risk_insights parameter has been removed from the response, which previously echoed the value sent in the request. The risk_insights parameter will always be included in the response.
How this may affect you
Performance and latency: This change will not affect the performance and latency of the API.
No action required: No changes or actions are needed on your part as a result of this update. If you include the parameter in the request, it will be ignored.
Who is affected: Customers using Intelligence and Verify Plus Products affected: Intelligence and Verify Plus
Changes
Unified risk recommendation ranges: We unified the numerical risk recommendation ranges for Intelligence 1.0 and 2.0 to improve the consistency of output and ease of configuration of your Intelligence solution. The risk recommendation scale used in Intelligence 1.0 is now the standard for all Intelligence models to improve clarity and better support future model development.
Details about the changes: The risk object contains these child properties – risk.level, risk.recommendation, and risk.score. There are changes to the risk.level and risk.score properties. Our Support Center article discusses these changes and provides a sample json file to help you understand whether this change may impact your configuration. Use this chart to understand the changes (marked as “new”) versus the prior Intelligence behavior (marked as “original”).
Original risk.score range
Original risk.level property value
New risk.score range
New risk.level property value
risk.recommendation property value (same for original and new)
101-450
very-low
1-200
low
allow
81-100
very-low
201-300
medium-low
allow
1-80
low
301-400
medium-low
allow
451-500
medium-low
401-500
medium
flag
501-600
medium
501-600
medium
flag
601-800
high
601-800
medium-high
block
801-1000
very-high
801-1000
high
block
How this may affect you
Performance and latency: Performance, latency and uptime of the API is not affected by the scale change.
Configuration: Depending on how you parse values, these changes could impact your configurations and require action:
If you are parsing values based off of the Intelligence risk recommendation scale or risk recommendation level, you were notified with a scheduled migration window to integrate with the new risk recommendation scale. If you have questions, please contact our Customer Support Team.
If you do not parse values based off the Intelligence risk recommendation scale or level, your API responses were not be impacted, and no action was required.
Who is affected: Full-service customers Products affected: Full-service portal
Changes
Updated design for reports: The UX for summary reports in the Full-service portal was updated so that it's clearer and more descriptive.
Transaction summary chart
Flexibility to filter for specific date ranges: A new date-picker for summary reports provides quick-selection options as well as more control over specific dates. You can now choose specific date ranges within a month rather than only month-by-month date ranges.
Availability: These changes affect summary reports on the Messaging API, Verify API, and Phone ID product pages in the Full-service portal as well as its main account page.
Go to our developer documentation for Voice for more information about our Voice product. If you are new to Telesign or have questions regarding Telesign's Voice product, please contact us.
Who is affected: Verify API customers Products affected: Verify API
Changes
Support for Silent Verify and Push Verify in iOS applications: Our new iOS SDK allows developers of iOS mobile applications to use Silent Verify and Push Verify through the Verify API.
Automatic fallback: Automatic fallback to OTP delivery channels is supported by our Mobile Verify SDKs.
iOS and Android device support: You can utilize these verification channels across both iOS and Android devices.
How this may affect you:
Integration: You can integrate the Verify API SDK into your mobile apps using the current versions of Silent Verify and Push Verify with fallback verification channels.
Scaling: With a single integration, you can scale new authentication channels with minimal development resources.
Additional information
If you are new to Telesign or have questions regarding our Mobile Verify iOS SDK, please contact us.
Who is affected: Verify API customers Products affected: Verify API
Changes
New parameter: The message_template parameter was added to Create a verification process. Declare a template once for the entire verification process. The template is available for use on all channels. If a template isn't specified, Verify API will use a default template. Contact our Customer Support Team to assist you in creating a template before using this parameter.
New template specification guide: We added a new guide, Verify API - Specify Verify API template which explains step-by-step how to specify a Verify API template using this new parameter.
New verification policy and fallback time: Our new guide explains how to use verification_policy when you create a verification process. The guide also discusses default verification methods, fallback times, and restrictions when using the verification policy feature.
Fixed routing by country: We added a new guide which discusses this feature. Fixed routing by country allows you to manage verification methods for each country, providing enhanced control and flexibility. Contact our Customer Support Team to set up specific routing preferences.
Code validity: This feature, which is discussed in this new guide, allows you to specify the length of the code validity duration, maximum number of attempts, and the length of the code generated by Telesign for any one-time passcode (OTP) method you use. Contact our Customer Support Team to enable this feature and change the default values.
Who is affected: Messaging customers Products affected: Messaging
Changes
Authentication using a voice call: use the new otp_code and the language parameters to define authentication via voice call for an end user. This authentication use case requires using otp_voice as the template name. See Messaging - Authenticate using voice call for more information.
Robust text-to-speech language support: This new feature utilizes the same collection of languages used by our Voice product. See Voice - Supported languages for text-to-speech for a complete list of languages.
Support for Transaction Callback Service and GetStatus: These optional features which provide additional details regarding your transactions are available when authenticating a voice call using Messaging. Contact our Customer Support team for more information.
