- Release Notes and Announcements
- Announcements
- Price Adjustment of Global SMS in Certain Countries/Regions on September 1, 2024
- Price Adjustment of Global SMS in Certain Countries/Regions
- Optimization of Tencent Cloud SMS Template Types
- SMSes in Malaysia prohibited from containing URLs, phone numbers and requests for personal numbers
- Prohibition on Sending Non-compliant Messages
- Adjustment of Calculation Rule for Global SMS Message Length
- Price Adjustment of Global SMS
- Announcements
- Product Introduction
- Review Standards
- Global SMS
- Console Guide
- Practical Tutorial
- API Documentation
- SDK Documentation
- FAQ
- Service Agreement
- Contact Us
- Release Notes and Announcements
- Announcements
- Price Adjustment of Global SMS in Certain Countries/Regions on September 1, 2024
- Price Adjustment of Global SMS in Certain Countries/Regions
- Optimization of Tencent Cloud SMS Template Types
- SMSes in Malaysia prohibited from containing URLs, phone numbers and requests for personal numbers
- Prohibition on Sending Non-compliant Messages
- Adjustment of Calculation Rule for Global SMS Message Length
- Price Adjustment of Global SMS
- Announcements
- Product Introduction
- Review Standards
- Global SMS
- Console Guide
- Practical Tutorial
- API Documentation
- SDK Documentation
- FAQ
- Service Agreement
- Contact Us
SDK 3.0 is a companion tool for the TencentCloud API 3.0 platform. You can use all SMS APIs through the SDK. The new SDK version is unified and features the same SDK usage, API call methods, error codes, and returned packet formats for different programming languages.
Relevant documentation and SDK source code can be obtained as follows:
Platform | SDK Documentation | GitHub Address |
Java | ||
PHP | ||
Python | ||
JavaScript | ||
C# | ||
Go | ||
C++ |
Note:
All the SMS SDKs in this document are on the latest 3.0 version, and new SMS features will be updated here. You are strongly recommended to use SDK 3.0 and the supportive API 3.0.
Existing APIs and SDKs on version 2.0 are still available but may be disused in the future.
Yes
No
Was this page helpful?