We’re making an important change to how we deliver Box SDKs.
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.
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.
Here’s what this means for your applications and development workflow.
The bottom line
Your existing code continues to work. Applications using Box Next Generation SDKs will run without any changes. However, these SDKs won’t receive new features, updates, or bug fixes going forward. All future development will happen in the consolidated Box core SDK packages, starting with version v10.
What’s changing
We’re merging two separate SDK lines into one:
- Box core SDKs (manually maintained)
- Box Next Generation SDKs (auto-generated)
The new unified packages will deliver all capabilities in a single artifact per programming language, following industry best practices for SDK distribution.
Why this change?
This consolidation brings several benefits:
- Simplified migration between SDK versions
- Easier feature adoption for applications using core SDKs
- Unified development effort focused on a single SDK per language
- Industry-standard approach to SDK packaging
Migration path
The transition follows our standard SDK versioning strategy, which prioritizes backward compatibility while providing clear upgrade paths:
Version (n+1) - Transition phase
The next major version after current will include both core and Next Generation SDK artifacts. This allows you to use features from both SDKs simultaneously during migration.
Version v10.0.0 - Next Generation Only
Version 10 contains only the Next Generation SDK artifact, representing the future direction of Box SDKs.
Quick decision guide
Creating a new application?
Use v10.0.0 of the Box core SDK package.
Using Box Next Generation SDK?
Replace your package dependency with the Box core SDK v10.0.0. Your imports remain the same (except TypeScript, which requires minor adjustments).
Using Box core SDK?
When available, upgrade to the next major version to access both artifacts during transition.
Not planning changes?
Lock your package manager to your current SDK version to prevent unexpected updates.
SDK version reference
Next steps
- Review your dependencies — Check which Box SDK version your applications use
- Plan your migration — Most migrations require only a package name change
- Test thoroughly — While most code works unchanged, verify your specific use cases
- Lock versions if needed — Prevent automatic updates if you’re not ready to migrate
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:
The consolidation represents our commitment to providing a more streamlined developer experience while maintaining the reliability you expect from Box SDKs. We’re confident this change will make building with Box easier and more efficient.
