box-node-sdk

# Versioning Strategy

Starting with v10 of the SDK, we’ve introduced a new generated codebase designed to enhance your experience with the Box API.
It is currently available on the sdk-gen branch.

v10 is targeted at new users of Box Node SDK and users already working with the generated Box Typescript SDK previously available under the Box Typescript SDK Gen repository.

For users of v3 of the Box Node SDK, no action is required at this time — we’ll be providing an upcoming v4 release that will include code from both versions for a smooth migration path. To avoid unintentional upgrades, pin your version to box-node-sdk: ^3.8.2 in your package.json.

For full guidance on SDK versioning, see the Box SDK Versioning Guide.

Which Version Should I Use?

Scenario	Recommended Version	Example Dependency
Creating a new application	Use v10	npm install box-node-sdk@10
Existing app using box-sdk-gen artifact	Upgrade to v10	npm install box-node-sdk@10
Existing app using box-node-sdk and planning to use new features	Wait for v4 to start migration process	TBD
Existing app using box-node-sdk and not planning changes	Stay on your current version	npm install box-node-sdk@^3.8.2

Box Node SDK

We are excited to introduce the stable release of the latest generation of Box Node SDK, designed to elevate the developer experience and streamline your integration with the Box Content Cloud.

With this SDK, you’ll have access to:

• Full API Support: The new generation of Box SDKs empowers developers with complete coverage of the Box API ecosystem. You can now access all the latest features and functionalities offered by Box, allowing you to build even more sophisticated and feature-rich applications.
• Rapid API Updates: Say goodbye to waiting for new Box APIs to be incorporated into the SDK. With our new auto-generation development approach, we can now add new Box APIs to the SDK 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: We understand that easy access to information is crucial for developers. With our new approach, we have included comprehensive documentation for all objects and parameters directly in the source code of the SDK. This means you no longer need to look up this information on the developer portal, saving you time and streamlining your development process.
• Enhanced Convenience Methods: Our commitment to enhancing your development experience continues with the introduction of convenience methods. These methods cover various aspects such as chunk uploads, classification, and much more.
• Seamless Start: The new SDKs integrate essential functionalities like authentication, automatic retries with exponential backoff, exception handling, request cancellation, and type checking, enabling you to focus solely on your application's business logic.

Embrace the new generation of Box SDKs and unlock the full potential of the Box Content Cloud.

Table of contents

• Box Node SDK
• Table of contents
• Installing
• Getting Started
• Documentation
• Browser Support
• Upgrades
• Integration Tests
  • Running integration tests locally
    • Create Platform Application
    • Export configuration
• Questions, Bugs, and Feature Requests?
• Copyright and License

Installing

If you are using npm:

npm install box-node-sdk@<version>

If you use yarn, please do this instead:

yarn add box-node-sdk@<version>

Where VERSION is the version of the SDK you want to use. The next generation of the SDK starts with version 10.0.0.

Getting Started

To get started with the SDK, get a Developer Token from the Configuration page of your app in the Box Developer Console. You can use this token to make test calls for your own Box account.

The SDK provides an DeveloperTokenAuth class, which allows you to authenticate using your Developer Token. Use instance of DeveloperTokenAuth to initialize Client object. Using Client object you can access managers, which allow you to perform some operations on your Box account.

The example below demonstrates how to authenticate with Developer Token and print names of all items inside a root folder.

const { BoxClient, BoxDeveloperTokenAuth } = require('box-node-sdk');

async function main(token) {
  let auth = new BoxDeveloperTokenAuth({ token });
  let client = new BoxClient({ auth });
  let entries = (await client.folders.getFolderItems('0')).entries;
  entries.forEach((entry) => console.log(entry));
}

main('INSERT YOUR DEVELOPER TOKEN HERE');

In order to use in browser make sure you include the lib/bundle.js file and then you can access the classes like so:

const { BoxClient, BoxDeveloperTokenAuth } = window['box-node-sdk'];

See example.html for an example website using this SDK.

To run the example locally:

• Start the local server by running npx serve -p 3000 in the project directory.
• Make sure http://localhost:3000 is allowlisted in CORS Domains of your application.
• Head over to http://localhost:3000/example.html.
• Provide a fresh Developer Token to the dialog window that shows up upon running the example.
• Make sure that you get an alert message that includes your user name.

Documentation

Browse the docs or see API Reference for more information.

Browser Support

This SDK works in modern browsers that support ES6+ features. It seamlessly integrates with frontend frameworks like ReactJS, Angular, and NextJS. Check out our example below:

• React Sample App

Upgrades

Upgrading from our legacy SDKs to the new generation SDKs is a straightforward process. See our migration guide and changelog for more information.

Integration Tests

Running integration tests locally

Create Platform Application

To run integration tests locally you will need a Custom App created in the Box Developer Console with Server Authentication (with JWT) selected as authentication method. Once created you can edit properties of the application:

• In section App Access Level select App + Enterprise Access. You can enable all Application Scopes.
• In section Advanced Features enable Make API calls using the as-user header and Generate user access tokens.

Now select Authorization and submit application to be reviewed by account admin.

Export configuration

• Select Configuration tab and in the bottom in the section App Settings download your app configuration settings as JSON.
• Encode configuration file to Base64, e.g. using command: base64 -i path_to_json_file
• Set environment variable: JWT_CONFIG_BASE_64 with base64 encoded jwt configuration file
• Set environment variable: BOX_FILE_REQUEST_ID with ID of file request already created in the user account, BOX_EXTERNAL_USER_EMAIL with email of free external user which not belongs to any enterprise and BOX_EXTERNAL_USER_ID with its ID.
• Set environment variable: WORKFLOW_FOLDER_ID with the ID of the Relay workflow that deletes the file that triggered the workflow. The workflow should have a manual start to be able to start it from the API.
• Set environment variable: APP_ITEM_ASSOCIATION_FILE_ID to the ID of the file with associated app item and APP_ITEM_ASSOCIATION_FOLDER_ID to the ID of the folder with associated app item.
• Set environment variable: APP_ITEM_SHARED_LINK to the shared link associated with app item.
• Set environment variable: SLACK_AUTOMATION_USER_ID to the ID of the user responsible for the Slack automation, SLACK_ORG_ID to the ID of the Slack organization and SLACK_PARTNER_ITEM_ID to the ID of the Slack partner item.

Questions, Bugs, and Feature Requests?

Need to contact us directly? Browse the issues tickets! Or, if that doesn't work, file a new one and we will get back to you. If you have general questions about the Box API, you can post to the Box Developer Forum.

Copyright and License

Copyright 2023 Box, Inc. All rights reserved.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.