Box SDK versioning strategy

The Box core SDKs and the Box Next Generation SDKs were initially created as separate libraries. However, in keeping with industry best practices, we are consolidating the Box Next Generation SDKs and the Box core SDKs into a single package for each programming language. This makes migration efforts much easier and allows seamless addition of new capabilities to existing applications still powered by older versions of the Box core SDKs, which were maintained manually.

To facilitate this migration process, there are two actively maintained major Box core SDK versions:

• A major version that follows sequential versioning for each SDK artifact and includes: the manually maintained package and the generated one. This SDK version enables leveraging coexisting packages at the same time, and serves as a transition phase. Support for the consolidated version of each Box core SDKs will continue in 2027.
• v10 that includes only the generated package.

Here's what you can expect from generated packages of the Box SDK:

• Full API support: New Box SDKs empower developers with complete coverage of the Box API ecosystem. You can access all the latest features and functionalities offered by Box and build feature-rich applications.
• Rapid API updates: The new auto-generation development approach allows you to add Box APIs to SDKs at a much faster pace (in a matter of days). This means you can leverage the most up-to-date features in your applications without delay.
• Embedded documentation: All objects and parameters are documented directly in the source code of the SDK so all the necessary information is stored in one place.
• Enhanced convenience methods: The newly introduced convenience methods cover various aspects such as authentication, chunk uploads, exponential back-offs, automatic retries, type checkers that help to ensure that you’re using variables correctly, and much more.

What it means for your project

1. Existing App - the Box core SDK

If you have an existing application that relies on the Box core SDK and you wish to further develop your project:

Action Use the major version that includes consolidated packages. Start using convenience methods and new features from the generated package, and gradually migrate your codebase. Ultimately, migrate to the Box core SDK package (≥v10.0.0).

2. Existing App - the Box Next Generation SDK

If you have an existing application that relies only on the Box Next Generation SDK and you wish to further develop your project:

Action Replace the library name in your package manager with the Box core SDK package (≥v10.0.0). Check migration guides for detailed instructions.

3. Existing App - the Box core SDK and the Box Next Generation SDK

If you have an existing application that relies both on the Box core SDK and the Next Generation SDK:

Action Use the major version that includes consolidated packages. Ultimately, migrate to the Box core SDK package (≥v10.0.0).

4. A New Application

If you are creating a new application:

Action Use ≥v10.0.0 of the Box core SDK.

5. No Active Development

If you have an existing application that you don't plan to change:

Action Ensure your package manager includes the specific version to prevent accidental updates. We strongly recommend upgrading to the major version, which includes consolidated packages, to receive ongoing security patches and improvements.

Versioning overview

Box core SDK versions and artifacts overview

Box Next Gen SDKs deprecation

As of September 17, 2025 Box Next Generation SDKs are no longer supported as separate artifacts. Don’t worry, your existing code will continue to work without changes. You can still use your applications based on Box Next Generation SDKs with no impact, but you won't receive new features, updates, or bug fixes.

All future development, including new features and updates, will be delivered through the Box core SDKs. The standalone generated artifact was introduced in the version v10 of the Box core SDKs, and it is currently available as a separate branch.

Migration

Migration from manually maintained SDK version to the consolidated SDK version

Follow detailed migration guides to migrate from the manually maintained SDK version to the consolidated SDK version:

• Python v3 to v4
• Node v3 to v4
• Java v4 to v5
• .NET v5 to v6
• Swift v5 to v6

Once your project is upgraded, follow the migration guides and migrate to the generated package.

Migration to the generated package

Follow detailed migration guides to migrate to the generated package within the Box core SDKs.

• Python: migrate from boxsdk to box_sdk_gen package
• Node: migrate from box-node-sdk to sdk-gen
• Java: migrate migrate from com.box.sdk to com.box.sdkgen package
• .NET: migrate from Box.V2 module to Box.Sdk.Gen module
• Swift: migrate from BoxSDK module to BoxSdkGen module

Migration from the Box Next Generation SDKs to the Box core SDKs

Follow detailed migration guides to migrate from the Box Next Generation SDKs to the Box core SDK ≥v10:

• Python
• TypeScript/Node
• Java
• .NET
• Swift