Who is affected: Customers using the Telesign Full-service C# SDK and Telesign Self-service C# SDK
Products affected: Telesign Full-service C# SDK and Telesign Self-service C# SDK

Changes

• The Telesign Full-service C# SDK and Telesign Self-service C# SDK now support the latest .NET Core versions. The .NET Core supported versions for both C# SDKs are:

  • .NET Core 6, 7, 8, and 9.

• .NET Core warnings resolved: Some versions of .NET Core generated warnings. This issue has been fixed.

• The Telesign Full-service C# SDK and Telesign Self-service C# SDK now support .NET Framework v4.8+. Both SDKs no longer support the following older .NET Framework versions:

  • .NET Framework v4.5.2, v4.6, v4.6.1, v4.6.2, v4.7, v4.7.1, and v4.7.2.

How this may affect you

• Latest version support for .NET Core: If you are using modern versions of .NET/.NET Core actively supported by Microsoft, you can now integrate with Telesign with full confidence that Telesign supports your framework.
• .NET Framework users may need to update: If the .NET Framework version you are using is no longer supported by Telesign (see above), you should update to one of our supported .NET Core or .NET Framework versions.

Additional information

• Full-service C# SDK: Go to its GitHub Readme for the latest version range support or go to its changelog for more information.
• Self-service C# SDK: Go to its GitHub Readme for the latest version range support or go to its changelog for more information.
• For additional assistance, contact us.

Who is affected: Customers using the Telesign Full-service Node.js SDK
Products affected: Telesign Full-service Node.js SDK

Changes

• The Telesign Full-service Node.js SDK now supports Messaging and the Verify API: The addition of Messaging and Verify API to the Telesign Full-service Node.js 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 Node.js 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 the Telesign Full-service Ruby SDK
Products affected: Telesign Full-service Ruby SDK

Changes

• The Telesign Full-service Ruby SDK now supports Messaging and the Verify API: The addition of Messaging and Verify API to the Telesign Full-service Ruby 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 Ruby 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 the Telesign Full-service PHP SDK
Products affected: Telesign Full-service PHP SDK

Changes

• The Telesign Full-service PHP SDK now supports Messaging and the Verify API: The addition of Messaging and Verify API to the Telesign Full-service PHP 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 PHP 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 the Telesign Full-service C# SDK
Products affected: Telesign Full-service C# SDK

Changes

• The Telesign Full-service C# SDK now supports Messaging and the Verify API: The addition of Messaging and Verify API to the Telesign Full-service C# 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 C# 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 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.

Additional information

• Go to our developer documentation for Intelligence for more information about Intelligence. If you are new to Telesign or have questions regarding Telesign's Intelligence product, please contact us.

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”).

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:

1. 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.

2. 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.

Additional information

Go to our Support Center article for instructions and more information on this change. See developer documentation for Intelligence or Insights reason code mappings for more information about Intelligence.