Box SDKs are the primary way to integrate with the Box API, which is why our teams are dedicated to delivering you the best possible developer experience.
A month ago, we announced changes to Box SDK distribution and introduced a new major version (v10), which includes only the generated SDK package. With a goal of simplifying migration efforts, we are additionally releasing a new major version that consolidates generated Box Next Gen SDKs and Box core SDKs — previously developed as separate artifacts.
In this article, you’ll find a detailed breakdown of Box SDK versions and recommended paths for your projects.
Overview
Box Next Gen SDKs were created to provide an improved developer experience with full API support, rapid updates, embedded documentation, and enhanced convenience methods. Their architecture was unified across all supported programming languages through the generation process. With the latest release, you can leverage those advantages directly in the Box core SDK packages, which were historically maintained manually.
Box core SDK packages are currently available in two major supported versions:
- A version that follows sequential versioning for each SDK artifact. It includes two packages — the manually maintained package and the generated package. The coexisting packages provide easy access to the latest Box API features and support gradual migration to the standalone generated package (starting from version 10).
- Version 10, a consistent version number across all Box SDK artifacts. It includes only the generated package and introduces breaking changes.
Two latest major versions of Box core SDKs
To better understand what has changed, let’s look at the Box Python SDK as an example:
- Python SDK v4 includes the manually maintained package (boxsdk) and the generated package (box_sdk_gen).
- Python SDK v10 only includes the generated package (box_sdk_gen).
- The Python Next Gen SDK artifact is deprecated, and its functionalities are now available through box_sdk_gen in both v4 and v10.
Ultimately, we recommend migrating to v10 and beyond. Support for the consolidated version of each Box core SDK will continue in 2027. A detailed version breakdown for all Box SDKs is available in our developer documentation.
An initial step for projects based on the Box core SDKs is an upgrade to the version that consolidates the manually maintained package and the generated package. To get started, refer to the following migration guides:
Next, detailed migration guides are available for each SDK to help you migrate to the generated package:
- 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
Deprecation of Box Next Gen SDKs
As of September 17, 2025, the 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 applications based on Box Next Generation SDKs; however, 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 version 10 of the Box core SDKs.
We have prepared detailed migration guides to help you transition from the Box Next Gen artifact to v10 of the Box core SDKs:
What this means for your projects
If you’re still unsure which version to use, see the recommended actions for the following cases:
- If you have an existing application that relies only on the Box core SDK and you wish to further develop your project, use the major version, which 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).
- If you have an existing application that relies on the Box Next Generation SDK and you wish to further develop your project, replace the library name in your package manager with the Box core SDK package (≥v10.0.0). Check migration guides for detailed instructions.
- If you have an existing application that relies on both the Box core SDK and the Box Next Generation SDK and you wish to further develop your project,use the major version, which includes consolidated packages.
- If you are creating a new application, use v10 or higher of the Box core SDK.
- If you have an existing application that you don’t plan to change, ensure your package manager includes the specific version of the SDK version to prevent accidental updates. We strongly recommend upgrading to the major version that includes consolidated packages to receive ongoing security patches and improvements.
Where to get support
We recommend reporting questions and issues directly in the individual Box SDK repositories on GitHub. You can also post questions in the Box Community forum under the SDKs and Tools thread.
