# Sinch SDKs

The Sinch SDKs allow you to quickly start interacting with the suite of Sinch APIs inside your favorite programming languages.

Sinch SDKs offer a consistent standardized framework for functionality to address problems like pagination, error code response and language familiarity regardless of the underlying API setup.  For example, two common approaches to pagination are page-based and token.  Depending on the API, there are pros and cons to each approach.  However, in our SDKs, we provide a single iterator object you can use to parse through your results.

Our client is centralized around a single authentication model, ensuring support for all actively supported language versions, and reducing reliance on third-party libraries.

The Sinch SDKs allow you to quickly start interacting with the Sinch APIs using your favorite programming languages.  Currently we support the following languages:

Node.js SDK
Java SDK
Python SDK
.NET SDK
## Current SDK versions

| SDK | Current Major Version | Previous Major Version |
|  --- | --- | --- |
| Node.js | 1.* |  |
| Java | 2.* | 1.* |
| Python | 2.* | 1.* |
| .NET | 1.* | — |


### Voice API support by SDK version

Voice API v1 and Voice API v2 are separate APIs. Check which SDK versions support the API you use before you install or upgrade.

| SDK | Voice API v1 | Voice API v2 (Preview) |
|  --- | --- | --- |
| Node.js | 1.x | 1.6.0 and later |
| Java | 1.x and 2.x | 2.3.0 and later |
| Python | 1.x only | 2.2.0 and later |
| .NET | 1.x | Not supported |


Python SDK 2.0 removed Voice API v1
Python SDK 2.0.0 and later don't include Voice API v1. To use Voice API v1 with Python, stay on Python SDK 1.x. To upgrade to Python SDK 2.x, migrate to Voice API v2 and use version 2.2.0 or later. See the [Voice API v2 migration guide](/docs/voice-2.0/migration).

## Version support

The Sinch SDKs follow [Semantic Versioning](https://semver.org/) for version numbering. SemVer defines what changes are allowed in each type of release (major, minor, patch) but does not define a support or patching policy.

This section describes the support policy for these SDKs.

### Release cadence

A new major version will not be released until at least 6 months after the previous major version.

### Support policy

Patches are published only for the latest minor release within each supported major version. For example: if version 2.0 exists and 2.1.0 is released, patches will be applied to 2.1.x only. Users on 2.0.x will no longer receive patches and must upgrade to 2.1.x to get bug fixes and security updates.

| Version | Status | Support | Timeline |
|  --- | --- | --- | --- |
| Current major (latest released) | Fully supported | All new features, bug fixes, and security fixes | Ongoing |
| Previous major | Maintenance | Critical bug fixes and security fixes only, no new features | Begins when current major is released; ends when next major is released or 1 year from current release, whichever comes first |
| Older majors | End-of-Life (EOL) | No patches or support | — |


### What are critical bug fixes?

For the previous major version, we apply patches for:

- Security vulnerabilities
- Data loss risks
- Breaking compatibility issues


### If you're using an unsupported version

We recommend upgrading to a supported version to receive ongoing security and stability updates. Bug reports against unsupported versions are not prioritized and may not be addressed.

### Dependency security updates

We assess dependency vulnerabilities by severity level. High and Critical vulnerabilities (CVSS score ≥ 7.0) are backported to the latest minor release of both the current and previous major versions. Medium and Low severity vulnerabilities (CVSS < 7.0) are applied to the current major version only.