- Node
- Ruby
- Python
- PHP
- .NET
- Java
Upgrade from Node.js Legacy to v4.8.0 or Latest Version
Introduction
This is a major application update. Plivo recommends you always use the latest or an active version of our SDKs for guaranteed security, stability, and uptime. The active SDK versions are designed to handle intermittent and regional failures of API requests. In addition, they offer a host of security features, such as protection against DoS attacks and bot detection for suspicious user agents.Migrate your applications
Node.js version support
The 4.x version of the Plivo SDK is compatible with Node.js versions 5.5 and higher.Use the commandnpm install [email protected] to upgrade to the active version of the SDK, or npm install plivo@latest to upgrade to the latest version.After you upgrade to the latest version of the SDK, you should check every program that depends on it and make changes to the syntax for several kinds of operations. Here are examples of how coding differs between the deprecated legacy version of the SDK and the latest active versions.Import the SDK
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Initialize
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Access resources
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Send a message
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Retrieve a message
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
List all messages
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Upgrade from Ruby Legacy to v4.9.0 or Latest Version
Introduction
This is a major application update. Plivo recommends you always use the latest or an active version of our SDKs for guaranteed security, stability, and uptime. The active SDK versions are designed to handle intermittent and regional failures of API requests. In addition, they offer a host of security features, such as protection against DoS attacks and bot detection for suspicious user agents.Deprecation notice: We’re deprecating Plivo Ruby SDK legacy versions lower than v4.9.0 on January 31, 2022. If you use a deprecated version of our SDK after that date, your API requests and messaging may fail intermittently. Plivo will no longer provide bug fixes to these versions, and our support team may ask you to upgrade before debugging issues.
Migrate your applications
Ruby version support
The Plivo Ruby SDK supports Ruby 2.0 and higher.Use the commandgem install plivo -v 4.9.0 to upgrade to the active version of the SDK, or gem update plivo to upgrade to the latest version.After you upgrade to the latest version of the SDK, you should check every program that depends on it and make changes to the syntax for several kinds of operations. Here are examples of how coding differs between the deprecated legacy version of the SDK and the latest active versions.Import the SDK
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Initialize
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Access resources
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Send a message
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Retrieve a message
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
List all messages
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Upgrade from Python SDK Legacy to v4.9.0 or Latest Version
Introduction
This is a major application update. Plivo recommends you always use the latest or an active version of our SDKs for guaranteed security, stability, and uptime. The active SDK versions are designed to handle intermittent and regional failures of API requests. In addition, they offer a host of security features, such as protection against DoS attacks and bot detection for suspicious user agents.Deprecation notice: We’re deprecating Plivo Python SDK legacy versions lower than v4.9.0 on January 31, 2022. If you use a deprecated version of our SDK after that date, your API requests and messaging may fail intermittently. Plivo will no longer provide bug fixes to these versions, and our support team may ask you to upgrade before debugging issues.
Migrate your applications
Python version support
Version 4.x of the Python SDK requires at least Python version 2.7. It will work with later versions, including Python 3.x versions.Use the commandpip install --upgrade plivo==4.9.0 to upgrade to the active version of the SDK, or pip install --upgrade plivo to upgrade to the latest version.After you upgrade to the latest version of the SDK, you should check every program that depends on it and make changes to the syntax for several kinds of operations. Here are examples of how coding differs between the deprecated legacy version of the SDK and the latest active versions.Import the SDK
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Initialize
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Access resources
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Send a message
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Retrieve a message
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
List all messages
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Upgrade from PHP SDK Legacy to v4.25.0 or Latest Version
Introduction
This is a major application update. Plivo recommends you always use the latest or an active version of our SDKs for guaranteed security, stability, and uptime. The active SDK versions are designed to handle intermittent and regional failures of API requests. In addition, they offer a host of security features, such as protection against DoS attacks and bot detection for suspicious user agents.Deprecation notice: We’re deprecating Plivo PHP SDK legacy versions lower than 4.25.0 on January 31, 2022. If you use a deprecated version of our SDK after that date, your API requests and messaging may fail intermittently. Plivo will no longer provide bug fixes to these versions, and our support team may ask you to upgrade before debugging issues.
Migrate your applications
PHP version support
The 4.x version of the Plivo SDK is compatible with PHP versions 7.3 and higher.Use the commandcomposer require plivo/plivo-php:4.25.0 to upgrade to the active version of the SDK, or composer require plivo/plivo-php to upgrade to the latest version.After you upgrade to the latest version of the SDK, you should check every program that depends on it and make changes to the syntax for several kinds of operations. Here are examples of how coding differs between the deprecated legacy version of the SDK and the latest active versions.Import the SDK
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Initialize
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Access resources
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Send a message
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Retrieve a message
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
List all messages
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Upgrade from .NET SDK Legacy to v4.10.0 or Latest Version
Introduction
This is a major application update. Plivo recommends you always use the latest or an active version of our SDKs for guaranteed security, stability, and uptime. The active SDK versions are designed to handle intermittent and regional failures of API requests. In addition, they offer a host of security features, such as protection against DoS attacks and bot detection for suspicious user agents.Deprecation notice: We’re deprecating Plivo .NET SDK legacy versions lower than v4.10.0 on January 31, 2022. If you use a deprecated version of our SDK after that date, your API requests and messaging may fail intermittently. Plivo will no longer provide bug fixes to these versions, and our support team may ask you to upgrade before debugging issues.
Migrate your applications
.NET version support
The Plivo .NET SDK supports .NET applications written in C# and Visual Basic that utilize the .NET Framework version 3.5 or higher or any .NET runtime supporting .NET Standard v1.4.Use the commandUpdate-Package Plivo -Version 4.10.0 to upgrade to the active version of the SDK, or Update-Package Plivo to upgrade to the latest version.After you upgrade, you should check every program that depends on the SDK and make changes to the syntax for several kinds of operations. Here are examples of how coding differs between the deprecated legacy versions of the SDK and the latest active versions.Import the SDK
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Initialize
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Access resources
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Send a message
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Retrieve a message
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
List all messages
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Upgrade from Java Legacy to v4.8.0 or Latest Version
Introduction
This is a major application update. Plivo recommends you always use the latest or an active version of our SDKs for guaranteed security, stability, and uptime. The active SDK versions are designed to handle intermittent and regional failures of API requests. In addition, they offer a host of security features, such as protection against DoS attacks and bot detection for suspicious user agents.Deprecation notice: We’re deprecating Plivo Java SDK legacy versions lower than v4.8.0 on January 31, 2022. If you use a deprecated version of our SDK after that date, your API requests and messaging may fail intermittently. Plivo will no longer provide bug fixes to these versions, and our support team may ask you to upgrade before debugging issues.
Migrate your applications
Java version support
The Plivo Java SDK supports OpenJDK 8 and 11 and OracleJDK 8 and 11.Use the commandUpdate-Package Plivo -Version 4.10.0 to upgrade to the active version of the SDK, or upgrade to the latest version.After you upgrade to the latest version of the SDK, you should check every program that depends on it and make changes to the syntax for several kinds of operations. Here are examples of how coding differs between the deprecated legacy version of the SDK and the latest active versions.Import the SDK
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Initialize
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Access resources
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Send a message
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
Retrieve a message
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |
List all messages
| Legacy | Latest |
Copy Ask AI | Copy Ask AI |