New featuresImpactful changesPythonJava
End of Support for Obsolete Language Versions
As Box to prepares to release the next major versions of the Python and Java SDKs, this is an alert that support is ending for obsolete language versions.On January 17, 2022, major releases of the Python and Java SDK libraries are planned, ending support for obsolete language versions. The Python SDK will abandon Python 2.7 and Python 3.5 starting from versionv3.0.0 of the
Python SDK. The Java SDK will abandon Java 7 starting from version v3.0.0 of
the Java SDK. Applications using the Python or Java SDK can still use the
respective older versions of those libraries located in the GitHub
release section, but any future new features will not be available for use.Where to get support
Should you have any issues or need further guidance, please post a request to our developer forum for any help needed. You can also connect with the SDK team on the respective GitHub repository.New featuresWindowsSDKs
New featuresPythonSDKs
Box Python SDK v2.14.0 released
New Features and Enhancements
- Add
admin_logs_streamingsupport for events stream (#623) - Add
vanity_nameparameter for creating shared link to a file or folder (#637) - Add getting files and file versions under retention for a retention policy assignment (#633)
- Support base item operations for WebLink class (#639)
Bug Fixes
New featuresImpactful changesAPI
OAuth 2.0 Redirect URL Updates
Today, we released a new feature to the Box Developer Console, allowing developers to add multiple redirect URIs for an OAuth 2.0 application.Starting November 29, 2021, new applications using OAuth 2.0 will require the URIs set in the configuration tab of the Developer Console to strictly match the one used during redirect. In addition, both new and existing applications, will gain the ability to add multiple redirect URIs.For existing applications, the deadline to make changes to this URL and avoid service disruption is May 13, 2022.Updates
- The Box Developer Console OAuth 2.0 application configuration section has a new button to add multiple redirect URIs
- Redirect URIs now force strict checking to match the URI passed in and URIs configured in the OAuth 2.0 application configuration
- Updated the
redirect_uriquery parameter wording on theGET /authorizeendpoint page - Updated the OAuth 2.0 setup, with SDK, and without SDK guide pages
Where to get support
Should you have any issues or need further guidance, please post a request to our developer forum for any help needed.New featuresJavaSDKs
Box Java SDK v2.58.0 released
New Features and Enhancements
- SDK support for new GET /events
stream_type:admin_logs_streaming(#938) - Adding
BoxDeveloperEditionAPIConnection#getUserConnectionto indicate that we can use this connection for managed users or app users (#940)
Bug Fixes
- Fix for deprecated enums still being used (#931)
New featuresAPI
New Shield Download Event
Today, we released a newevent_type to the Enterprise Event stream
for downloads that are restricted based on a Shield access policy.If an admin creates a shield access policy that restricts downloads and an
end user is blocked from downloading a file, an event is produced
within the enterprise event stream. Events will also be generated
when a user is viewing a folder with a file restricted from download, viewing a
file in preview that is restricted from download, and when a user requests to
download a file through the API that is restricted from download. These events
follow the standard event object schema and the event_type value set
to SHIELD_DOWNLOAD_BLOCKED.Updates
- Added a new section to the Smart Access event trigger documentation
- Added
SHIELD_DOWNLOAD_BLOCKEDto the enterprise event list
Where to get support
Should you have any issues or need further guidance, please post a request to our developer forum for any help needed.New featuresImpactful changesAPI
New Event Stream Live Monitoring stream_type
Today, we released a newstream_type for the GET /events
API called admin_logs_streaming. This allows for near real time monitoring of
events after they happen in Box.We recommend that applications subscribing to live events through admin_logs
migrate to admin_logs_streaming for the lowest and most consistent latency.
This stream_type requires the user to be an enterprise admin or co-admin with
the permission to Run new reports and access existing reports.Updates
We have made several documentation updates to help you learn about the new option- Completely reorganized the events guide section for easier understanding, including adding additional information to all pages in the various sections
- Updated the OpenAPI specification for the
GET /eventsendpoint to include the newstream_typeoption ofadmin_logs_streaming - Added a new how to migrate
stream_typepage with steps on switching
Where to get support
Should you have any issues or need further guidance, please post a request to our developer forum for any help needed.API
Added Retention Policy Marker Based Pagination
Our OpenAPI specification has been updated for retention policy and retention policy assignment endpoints to show use ofmarker based pagination and
fields query parameters.Updates
The following updates were made:- Added
fields,limit, andmarkerquery parameters to theGET /retention-policiesandGET /retention-policies-id-assignmentsendpoints. - Added
limitandnext_markerto the response object for retention policies and retention policy assignments
Where to get support
Should you have any issues or need further guidance, please create a post on our developer forum for any help needed.New featuresAPI
Extend Retention Via Files API
Now, you can extend the retention date for a file that is already under retention using the newdisposition_at field. If the date is extended, it
cannot be reverted or updated to a date prior to the new date.Updates
- Added a
disposition_atfield to the File(Full) resource - Added a
disposition_atparameter to the PUT file endpoint - Added a note in the retention policy guide section
Where to get support
Should you have any issues or need further guidance, please post a request to our developer forum for any help needed.Box Windows SDK v4.0.0 released
Breaking changes
- Extract interfaces for BoxClient and Managers to improve testability (#603)
- Add BoxConfigBuilder and make BoxConfig immutable (#737)
- Expose tasks from async methods (#742)
- Use DateTimeOffset instead of DateTime (#749)
- Rework returned exceptions (#753)
- Upgrade .NET Standard to 2.0 (#755)
New Features and Enhancements
- Add ability to get files under retention for assignment and file versions under retention for assignment (#734)
- Add
is_collaboration_restricted_to_enterpriseflag support forFolderupdate (#732) - Replace insensitive language (#738)
- Add new, easier to use method for create terms of service user status (#740)
- Allow sort and direction parameter to be passed in when getting trashed items (#754)
- Add support for Task completion_rule field (#758)
- Add BoxSign API support (#765)
Bug Fixes
New featuresImpactful changesiOSSDKs
New featuresAPI
Box Sign Enterprise Events
Box Sign events are now available via the enterprise events stream. For full details, please see our Box Sign events guide.Updates
- Add sign request document events: created, converted, completed, cancelled and expired
- Add sign request signer events: assigned, viewed by signer, downloaded, forwarded, signed and declined
-
Add two new statuses:
downloadedanddownloaded and signed
New featuresImpactful changesUI Elements
Box UI Elements v14.0.0 released
14.0.0 (2021-10-20)
Bug Fixes & Features
This release fixes several bugs. For a full list, please see the release notesAPI
App Diagnostics Report Feedback
We recently started releasing the new App Diagnostics Report to customers, and we would love to hear your thoughts! Visit the forum post to provide any feedback.New featuresJavaSDKs
API
Update to Webhooks Response
The webhook response has been updated to show the correct Webhook (Mini) object in the entries array.Bug Fixes
- Added a
miniresource for Webhook - Corrected the get-webhooks response object
New features
New App Diagnostics Report
A new report will be gradually deployed to customers starting Thursday, October 7th, 2021. We plan to have the report released to all customers by October 25th.Developers can now review API activity for their applications by generating an App Diagnostics Report from the Developer Console. Checkout the guide to see the steps required to run a report!As always, if you have issues you may file a support ticket or post on our developer forum.APIUI Elements
Support for Adobe Creative Cloud Previews
In conjunction with WebApp preview, Adobe Photoshop, Illustrator, and InDesign files are now supported via API.Updates
Files with extensionsindt, idml, indd, and inx are supported by:New featuresPythonSDKs
New featuresImpactful changesNodeSDKs
UI Elements
EOS for Open With UI Element and EOL for Adobe Sign
Today, the Open With UI element can integrate with Box Tools, Google Workspace, and Adobe Sign. In an effort to continuously improve the Box experience, we are focusing our resources on new features and functionality that better align with our users’ evolving needs.December 21, 2021 the following changes will occur:- We will discontinue support of the Box Open With UI Element for Box Tools and Google Workspace for any new customers. A new customer is any customer not using this element prior to December 21. Any customers leveraging the Open With UI Element with Box Tools and/or Google Workspace prior to December 21 are considered existing customers and will continue to receive support until further notice. The Box Tools and Google Workspace Web App functionality will not be impacted.
- Adobe Sign will no longer be available for use by new or existing customers via the Open With UI element or Web Application.
New featuresAPI
New enhancements to retention APIs
Two new API endpoints have been introduced to get files and file versions that are under retention for a given retention policy assignment. These APIs are part of the retention policy suite of APIs. They are intended to replace the separate file and file version retention endpoints, which will soon be deprecated from the Box API. The date of the deprecation will be announced at a later date.When a retention policy is applied via a retention policy assignment, folders are selected for which the retention policy should be applied. The files and file versions within those folders will be the content that is returned from calling these new endpoints.Features
This release has introduced the following new content and features.- Get files under retention: Returns a list of files under retention that are associated with the specified retention policy assignment.
- Get file versions under retention: Returns a list of file versions under retention that are associated with the specified retention policy assignment.
- Added an editable
descriptionfield to the retention policy resource. - Added a non-writable
start_field_dateto the retention policy assignment resource. This field is the metadata field’s key id. The value can also beupload_dateif theassigned_totype is notmetadata_templateor a date field has not been selected.
New featuresAPI
Classification Name Field now in Events API
If a classification exists on content, the events API now returns the classificationname field in the response object.- The updates to the event source response object can be seen here.
- A new guide page has been added to show examples for an event triggered by a user source and an event source.
Where to get support
Should you have any issues or need further guidance, please post a request to our developer forum for any help needed.API
Notice of behavior change for item preview events
Starting today, we will begin rolling out changes to the behavior of item preview events when an application consumes those events from our event API endpoints.This change will only affect theITEM_PREVIEW user event and will not affect existing
enterprise events. The new behavior will not cause
downtime within existing applications or require any application changes to
prevent uptime disruptions.Change overview
Within the previous behavior when events were consumed, previewed item events were surfaced through theITEM_PREVIEW event type for the owner of
the content as well as any contributors assigned to the content. This meant
that if a file with 2000 collaborators on it was previewed, the file owner
plus all 2000 collaborators would have an event created stating that the file
was previewed.With the new behavior, notification of an item being previewed will only be
created for the owner of the content and will not be produced for
collaborators. This will help to reduce the noise of the event stream while
preserving the ability to see when items are previewed as a content owner.Where to get support
Should you have any issues or need further guidance, please post a request to our developer forum for any help needed.New featuresJavaSDKs
New featuresNodeSDKs
Impactful changesAPI
Upcoming change to JWT format
On August 4th, 2021, as part of our continued infrastructure upgrades, we will begin deployment of a change that may affect custom applications leveraging Server Authentication with JSON Web Tokens (JWT).Potential impact will require additional verification from customers who do not use an official Box SDK and are storing tokens in a database.All customers and application owners who are potentially impacted have been notified directly via email.Change overview
This change may only impact applications leveraging Server Authentication with JSON Web Tokens (JWT). Tokens will continue to return as a string as stated in our documentation. However, the format will be longer and containspecial characters.An example of a token returned today:NXWd9KDPVofXQKZJlQjICCWFHEmuOihs.After this change, tokens will return in the following format:1!yxxhRreQCKcEbC_ZfYvPudyLe7Ed36gIQcqqZo2pfaVZyxNBkQjoHk0fgA1iTY3_uwXgif-hg-gne aUdLRmGCb2He6tyQ_rA8aV-CllTyBbd9Tx-wU6Fnt4Df9XjzBAk8Dj7RYc1Ew_fcY2vfycpCvjwHLgql jzjEpVIrOpOlK_2AyP5FExzn0x7DtbkaGc6avJU8UMQd_huXoJ7CnXIL_JBzVrW4D32pBLQ2AZIuecOZ NMIy9T8PdUiZIG6xKEPqYmm21mQHEM0d7dT5foSBtjm65-Ah2tb2MdSGFb1G1O24vz2GmYFgmIe5UOol qYIGg-0u2xQPC3F76WiNCiU_TP1JDQYi3HKaos807WkRtnBY5Vd-VAbY9DH-Qo3u1EiB0RFr4cht2N7V B99y-379IEYzCojL2V58dE_pBxpRMv4KcOLVsUfDkbx3uo34H4UzOycI_IWGWrhVJD4M7GeLeD_5Vkmj fbwYl2CmHdXAKbZKtXTHjzB0CZixZriT_wRUpsN8GTrrxGbx9ukgzJWRJwelGZ_1Yx7vP4Zkx3OfR5Be -Tso7xdHd9rW0FXsu024U7dMNuQ6kpP1_kJI2Y.Please note that this is not a new format to Box, as this format is currently
returned when downscoping tokens.Verifying application impact
- Navigate to Admin Console > Apps Tab > Custom Apps.
- Click View for each app row listed
- Scroll to the bottom of the app details page and verify the selected authentication method. Affected apps will say Server Authentication with JSON Web Tokens.
- Is it using an official Box SDK? If so, no further action is required to prepare for this change. While it is always best practice to be on the latest version, no minimum versions are required for compatibility.
- If an official SDK is not used, are tokens stored in a database? If so, you will need to preform additional verification that the database can handle both the new length and special characters.
Testing before release
If you have identified an application that leverages Server Authentication with JWT and stores tokens in a database, you will want to preform the test below before August 4th.As mentioned above, the new format for tokens is currently used when downscoping tokens. Therefore, preform the following steps to assess impact:- Generate an Access Token for the application
- Downscope the token from step 1
- Attempt to store the downscoped token in your database
Where to get support
Should you have any questions or need further guidance, please email jwt-set-rollout@box.com.API
New Getting Started Guide
Check out our step by step guide to getting started with the Box API. Discover best use cases, user models, architecture patterns, and more.Features
JavaSDKs
New featuresAPIJava
Release of Box Sign API
Today, July 26th, 2021, beings the roll out of Box Sign! Programmatically harness the full functionality of the Box Sign web app experience by leveraging our newest API endpoints to create, list, resend, and cancel Box Sign requests.While Box Sign does not need to be enabled by an Admin to use its API endpoints, it does need to be rolled out to your enterprise. We will notify Admins as it becomes available for their Box instance.At a minimum, creating a Box Sign request requires selecting a file for signature, a destination folder for the signed document/signing log, and designating signers. At this time, only one file can be signed per request.Features
- Add endpoint to create Box Sign requests: Guide | API reference
- Add endpoint to list Box Sign requests: Guide | API reference
- Add endpoint to get Box Sign requests by ID: Guide | API reference
- Add endpoint to resend Box Sign requests: Guide | API reference
- Add endpoint to cancel Box Sign requests: Guide | API reference
- Java SDK support: GitHub
New featuresJavaSDKs
Box Java SDK v2.55.0 released
NOTE: Due to the benign nature of the “breaking change” below, we decided NOT to increment the major version for this release. There should be no customer impact due to this change.Breaking Changes
- Update execute metadata query to match API response (#890)
- NOTE: This change removes a method without deprecating it. It was not possible to use the method correctly at all, because the underlying service no longer supported it.
New Features and Enhancements
- Remove or deprecate insensitive language ([#889])(https://github.com/box/box-java-sdk/pull/889)
- Add support for
is_external_collab_restrictedparameter for User (#896) - Add configurable permissions support for
GroupMembership(#897) - Add
SHIELD_JUSTIFICATION_APPROVALevent type (#898) - Add ability to get files under retention for assignment and file versions under retention for assignment (#899)
- Add
TASK_UPDATE,FILE_VERSION_RESTOREandADVANCED_FOLDER_SETTINGS_UPDATEevent types (#902) - Add Box Sign API support (#904)
Bug Fixes
API
Updated file size limits
Today we released our newest business plan, Enterprise Plus, which supports uploads and downloads up to 150GB. In addition, we upgraded file size limits for some of our existing plans, as detailed below. For details on how to confirm the file size limit for your account, please visit our upload guide.Updates
- Enterprise: 50 GB
- Digital Workplace Suite: 50 GB
- Digital Workplace Global Suite: 50 GB
- Digital Business Suite: 50 GB
- Digital Business Global Suite: 50 GB
- Enterprise Plus: 150 GB
New featuresAPI
New Manual Start Workflow Endpoints
Two new API endpoints have been introduced for Box Relay- Get workflows configured on a folder
- Start a manual start flow within a workflow for file(s)
trigger_type
of WORKFLOW_MANUAL_START. There is an optional outcome_parametes object
within the post request body. If your flow is configured to accept selections
at start time, you will need to send in these as a parameter. A guide with all
the options you can send in will be made available soon.Features
This release has introduced the following new content and features.API
Notice of behavior change for item open events
Starting today, we will begin rolling out changes to the behavior ofITEM_OPEN events when an application consumes those events from our
event API endpoint.This change will only affect the ITEM_OPEN enterprise event.
The new behavior will not cause downtime within existing applications or
require any application changes to prevent uptime disruptions.Change overview
Within the previous behavior when events were consumed, opened item events were surfaced through theITEM_OPEN event type for the owner of the content as
well as any contributors assigned to the content. This meant that if a file with
2000 collaborators on it was opened, say on Drive, the file owner plus all
2000 collaborators would have an event created stating that the file was opened.With the new behavior, notification of an item being opened will only be created
for the owner of the content and will not be produced for collaborators. This
will help to reduce the noise of the event stream while preserving the ability
to see when items are opened as a content owner.Where to get support
Should you have any issues or need further guidance, please post a request to our developer forum for any help needed.PythonSDKs
NodeSDKs
NodeSDKs
New featuresImpactful changesUI Elements
Box UI Elements v13.0.0 released
13.0.0 (2021-04-22)
Bug Fixes & Features
This release fixes several bugs. For a full list, please see the release notesBox iOS SDK v4.4.0 released
Breaking Changes
New Features and Enhancements
- Add support for search parameter to get shared link items (#756)
- Add support for folder lock functionality (#759)
- Add support for
copyInstanceOnItemCopyfield for metadata templates (#763) - Add support for stream upload of new file versions and add support for ‘If-Match’ header when uploading new file versions (#766)
- Add additional details field for
Eventmodel (#770)
Bug Fixes:**
New featuresPythonSDKs
New featuresNodeSDKs
API
Notice of behavior change for item download events
Starting today, we will begin rolling out changes to the behavior of item download events when an application consumes those events from our event API endpoints.This change will only affect theITEM_DOWNLOAD user event and will not affect existing
enterprise events. The new behavior will not cause
downtime within existing applications or require any application changes to
prevent uptime disruptions.Change overview
Within the previous behavior when events were consumed, downloaded item events were surfaced through theITEM_DOWNLOAD event type for the owner of
the content as well as any contributors assigned to the content. This meant
that if a file with 2000 collaborators on it was downloaded, the file owner
plus all 2000 collaborators would have an event created stating that the file
was downloaded.With the new behavior, notification of an item being downloaded will only be
created for the owner of the content and will not be produced for
collaborators. This will help to reduce the noise of the event stream while
preserving the ability to see when items are downloaded as a content owner.Where to get support
Should you have any issues or need further guidance, please post a request to our developer forum for any help needed.New featuresAPI
New option for downscoping tokens using shared links
When requesting an access token, you now have the ability to downscope that token to a file or folder using a shared link.This new parameter may be used instead of using theresource parameter, which allows you to supply a file or folder ID to perform the same action.Updates
- Added new
box_shared_linkrequest parameter to downscoping documentation. A shared link may be supplied to downscope an access token in the below way.
- Added
box_shared_linkrequest parameter to request access token API reference.
New featuresJavaSDKs
New featuresAPI
Service Account email added to Developer Console
Upon Admin authorization of an application leveraging server authentication, the auto-generated email address of the Service Account is now surfaced in the General tab of the Developer Console. This email address can then be used to collaborate the user on Box content. The format will always beAutomationUser_AppServiceID_RandomString@boxdevedition.com. For example,
AutomationUser_123456_6jCo6Pqwo@boxdevedition.com.To learn more, see our guide on User Types and Service Accounts.Features
- Added auto-generated email address of Service Account user to Developer Console
New featuresAPI
New Metadata Query Indices Endpoint
A new API endpoint has been introduced to get a list of metadata query indices for a given template and scope.Metadata queries provide a way to find files and folders by searching for the metadata attached to them.When performing metadata queries on 10,000 or more files or folders, non-performant queries may produce anHTTP 403 error.
Creating a search index delivers the ability to run
these queries at scale to bypass this error state, and are automatically applied
during the querying process.The new endpoint permits the lookup of these created search indices.Features
This release has introduced the following new content and features.- New API endpoint to get a list of metadata query indices by scope and template.
- New metadata query index response object.
- New metadata query indices response object.
Updates
This release includes the following updated content.- Updated metadata query indices guide to include details on how to get a list of metadata query indices.
New featuresAPI
New Collection Events
External collection events are now available via the enterprise events stream.Collections in Box are a way to group files, folders, and web links without putting them all into a folder together. These new events provide a method for monitoring when collection actions are taken within an enterprise.The events follow the standard event object schema, and include the following:COLLECTION_CREATE: A collection was createdCOLLECTION_DELETE: A collection was deletedCOLLECTION_UPDATE: A collection was updatedCOLLECTION_ITEM_CREATE: An item was added to a collectionCOLLECTION_ITEM_DELETE: An item was removed from a collectionCOLLECTION_ITEM_UPDATE: An item in a collection was updated
New featuresAPI
Box Shield Smart Access events
External collaboration restriction and justification approval events are now available via the enterprise events stream.Box Shield must be purchased and enabled on a Box enterprise in order to take advantage of these advanced security offerings.These events follow the standard event object schema, with theevent_type value set of:
SHIELD_EXTERNAL_COLLAB_INVITE_BLOCKED_MISSING_JUSTIFICATION,
SHIELD_EXTERNAL_COLLAB_INVITE_JUSTIFIED,
SHIELD_EXTERNAL_COLLAB_INVITE_BLOCKED
SHIELD_EXTERNAL_COLLAB_ACCESS_BLOCKED_MISSING_JUSTIFICATION,
SHIELD_EXTERNAL_COLLAB_ACCESS_BLOCKED, or
SHIELD_JUSTIFICATION_APPROVAL.The additional_details payload of each event provides more information. Full
details can be found in our [Shield Events guide.Features
- Add support for Box Shield external collaboration and justification approval events to the enterprise events stream
New featuresCLI
SalesforceImpactful changesAPI
Box API response header changes that may impact your applications
On May 10th, 2021, as part of our continued infrastructure upgrade, Box’s API response headers will standardize to always return in a case-insensitive manner, in line with industry best practices and our API documentation.This change has the following potential impact:- Salesforce SDK
v1users will be impacted and will need to upgrade to a recent SDK version. Not doing so will cause your Box Salesforce integration to cease functioning after May 10th, 2021. - Box API consumers who do not use one of the Box SDKs may be impacted and will need to verify header usage through their code. Depending on your header usage, not making adjustments may cause disruptions in your Box API integration.
Change overview
Applications that are using the return headers described above, such aslocation and retry-after, will need to verify that their applications are
checking for these headers in a case-insensitive fashion. Over the past 12
months Box has been upgrading its networking and observability infrastructure.
These upgrades aim to improve reliability and availability of Box’s products
for our customers. This specific change allows Box to deploy an updated service
proxy, enabling Box to better monitor service traffic, quickly find
problem areas, and tune application performance.API Consumers: Verifying application impact
Verifying whether your application(s) will be impacted will require a review of your code. If you are solely using one of the official Box SDKs to connect to Box APIs, you will not be impacted as the SDKs handle response headers in a case-insensitive manner.You may verify whether you are impacted with the following steps:- Locate the code in your application which handles the responses from Box API requests. If you are not extracting the response headers from these responses, you are not impacted.
- If you are extracting those response headers, you may be impacted if you are expecting those headers in a case-sensitive fashion.
Location header to be returned with a
starting capital L, a direct string comparison with a specific case, then
your code will need to be altered to prevent it from breaking after the change
is made.API Consumers: How to make the change
To update the impacted application(s), ensure that you are checking these response headers in a case-insensitive manner. Specifically, your code should be built in a defensive way to ensure that if a header, such asLocation, is
sent with an initial capital L or a lowercase l, it’ll be handled in the
same way. For example, forcing all headers to lowercase before checking, or
using a case-insensitive regex string check, are two viable methods for
handling this process.Salesforce SDK v1 users: Verifying application impact
If you are unsure whether you are using v1.0 of the Box Salesforce SDK, go to
the application code location where you have stored the Box Salesforce SDK and
do the following:Load the following Salesforce SDK file: src/classes/BoxApiRequest.clsLook for the following lines (should be lines 6-7):v1.1.0 or later of the
Salesforce SDK, which is not impacted and no changes are needed. If those lines
are not present then you are using v1.0 of the Salesforce SDK, which will be
impacted and will need to be updated.Salesforce SDK v1 users: How to make the change
To update the impacted application(s), you will need to update the version of
the Salesforce SDK that you are using. It is recommended that you upgrade to
the most recent version of the SDK, but anything from
v1.1.0 or later will be adequate to ensure that
there is no impact to your application(s).Where to get support
Should you have any issues or need further guidance, please file a ticket with our support team or post a request to our developer forum for any help needed.New featuresiOSSDKs
New featuresNodeSDKs
API
Maximum upload file size limit increases
The maximum file size that may be uploaded via the API has been increased for the following Box account plans.- Business Plus
- Enterprise
- Digital Workplace Suite
- Digital Workplace Global Suite
API
Metadata Query index changes
When making file / folder metadata query requests, a search index needs to be created for queries where more than 10,000 files / folders are being searched.To improve the efficiency and simplicity of this process, we have changed the way in which indexes are used by removing the explicit requirement to supply an index through theuse_index key in a metadata query API request.There is no impact to existing applications that are currently supplying an
index through the use_index key. The supplied index will be ignored in
the request and the most efficient index will be automatically applied.Previous Indexing Process
The following was the previous process for creating and using an index for a metadata query request involving 10,000+ files / folders in the search. This is the process being replaced.- Contact the metadata query team to request an index.
- The metadata query team would create the index and supply back the name of the newly created index.
- When making metadata query requests this index name was
supplied as the value for the
use_indexkey in the API request.
New Indexing Process
The following is the new process for creating and using an index.- Contact the metadata query team to request an index.
use_index key within the metadata query API request has been removed.
Instead, the most efficient query will be automatically applied during the
search process.Indexes that are currently supplied in the use_index key will be ignored, and
instead the most efficient index will be used.Application owners may safely remove the use_index key and value from their
metadata query requests at their discretion.New featuresAPI
Developer Console Updates
A new Authorization tab is now available in the Developer Console. In addition, clarifying UI changes were made to the Application Access and Scope settings within the Configuration tab to ease these decisions. These changes do not impact the functionality of the settings.Now, developers will navigate to the Authorization tab to submit the application directly to their Box Admin for authorization approval.As for the Configuration tab, helpful tips were added to the JWT Application Access settings to facilitate a clear decision between App Only Access or App Access + Enterprise Access. The Scope section is now grouped by action type: content, administrative, and developer.Updates
- Added Authorization tab to the Developer Console
- Updated the UI for JWT Application Access settings under the Configuration tab
- Updated the UI grouping of Scopes under the Configuration tab
New featuresPythonSDKs
