Box SDK versioning strategy

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.

Why we are making this change

In keeping with industry best practices, we are consolidating the Box Next Generation SDKs and 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 Box core SDKs, which were maintained manually.

All future development, including new features and updates for the Next Generation SDKs, will be delivered through Box core SDKs starting with version v10. Currently, v10 is available as a separate branch.

How it will work

Box core SDKs and Box Next Generation SDKs were created as separate libraries. Going forward, the Box core SDK artifacts will include:

• (n+1) major version will include manually maintained Box core SDK and Box Next Generation SDK artifacts. This version enables leveraging coexisting artifacts at the same time, and serve as a transition phase. Stay tuned for this upcoming release.
• v10.0.0 version includes only the Box Next Generation SDK artifact. Currently, this version is available as a branch for each SDK repository.

How to decide

1. If you are creating a new application, use v10 of the Box core SDK package.
2. If you have an existing application relying on the Box Next Generation SDK and you wish to further develop your project, replace the name of this library in the package manager with the Box core SDK package (v10.0.0). Object imports for most SDKs will persist the same and your code will work as-is; the TypeScript SDK requires additional steps for migrating. Check the section below for detailed guides.
3. If you have an existing application relying on Box core SDK and you wish to further develop your project, once released, bump the library version by one major release. See the table above for a detailed breakdown of recommended versions.
4. If you have an existing application that you don’t plan to change, ensure your package manager includes the version of SDK you are using to prevent an accidental rebuild that pulls in a version you aren’t expecting.

Versioning overview

Box SDK versions and artifacts

Box Next Gen SDK deprecation status

Migration

Migrating from Box Next Generations SDKs to core Box SDK v10

Follow detailed migrations guides to migrate from from Box Next Generations SDKs to Box core SDK v10:

• Python
• TypeScript
• Java
• .NET
• Swift