Box Sign API supports setting redirect URLs
Box Sign API supports setting redirect URLs
The Box Sign API now offers new parameters to set up custom redirect URLs for users who sign or decline a sign request. This way, when integrating your application with Box Sign, you can redirect the signers back to your application or display a custom landing page.
Updates
Box Sign API provides optional parameters to pass in the request body of the Create Sign Request call:
redirect_url
that redirects the user to a specific page after signing a requestdeclined_redirect_url
that redirects the user to a specific page after declining a request
You can define redirect URLs globally for all signers and for specific signers only. For details, see the Create Sign Request guide.
Developer Resources
Are you interested in creating applications for the Box App Center or becoming a Box Partner? Check out the Box Partner Resources guides for more information!
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 CLI v3.1.0
released
Box CLI v3.1.0
released
New Features and Enhancements
- Add --all flag for search to return all results (#336) (
23ea0a5
) - add unique state parameter to
OAuth2
login (#292) (5ce6a40
) - allow changing base URLs (#303) (
e284059
) - obtain
oauth
authorization from command line (#299) (18c88bb
) - use native credential storage for MacOS and Windows (#295) (
74c4922
)
Bug Fixes
users:transfer-content
to respect quiet flag (#288) (1d0bbab
)- correctly pass
copy-instance-on-item-copy
flag (#285) (cd4fbf4
) - Fix updating webhook triggers (#297) (
09e94c3
) - support large output when using
json
flag by replacingjson.stringify
(#328) (1204f2c
) - Support limit flag for Box Search (#323) (
0009a77
), closes #322 - Support OAuth with multiple redirect URIs (#302) (
9fe216e
)
Box Windows SDK v4.4.0
released
Box Windows SDK v4.4.0
released
New Features and Enhancements:
- add
can_edit
field toSharedLink
(#831) (e0d4197
) - add
version_number
toBoxFileVersion
(#820) (f174358
) - add upload and delete support for Avatar API (#829) (
4dcb84a
)
Bug Fixes:
- Fix initialization of
BoxAPIException
object (#828) (a298f01
) - properly dispose response on exception (#819) (
8415bd3
)
New Box App Center (formally App Gallery)
New Box App Center (formally App Gallery)
You can now visit the completely updated Box App Center to find the over 1500+ integrations you already know and love.
Updates
Box App Center provides a modernized catalog of apps and integrations and will be accessible from the Box Web app.
For end-users, the Box App Center makes it smoother to work the way you want to, thanks to the comprehensive selection of ready-to-use integrations from partners such as Microsoft, Zoom, Salesforce, and Slack, to name a few.
For IT leaders and admins, the Box App Center gives your users choice, without sacrificing security or user experience. And it eliminates shadow IT by providing a list of enterprise-approved options.
Box App Center will be part of the Core Box package; The Box App Center is available to all customers today!
Developer Resources
Are you interested in creating applications for the Box App Center or becoming a Box Partner? Check out the Box Partner Resources guides for more information!
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 Endpoints to Manage User Avatars
New Endpoints to Manage User Avatars
Starting today, the User Avatar APIs supports adding, updating, and deleting user avatars.
To create or update a user avatar, call the POST /users-id-avatar
endpoint. Remember to include the path to the file you want to upload. If an avatar already exists, it will be replaced with the new photo uploaded.
curl -i -X POST -L https://api.box.net/2.0/users/userID/avatar
-H 'Authorization: Bearer <ACCESS_TOKEN>'
--form 'pic=@"path/to/file/file.jpeg"'
The response includes the user avatar object with URLs to the file location.
To delete a user avatar, call the DELETE /users-id-avatar
endpoint:
curl -i -X DELETE -L https://api.box.net/2.0/users/userID/avatar
-H 'Authorization: Bearer <ACCESS_TOKEN>'
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.
OAuth 2.0 Redirect URL Strict Checking Enabled
OAuth 2.0 Redirect URL Strict Checking Enabled
Today, we turned on strict checking for all OAuth 2.0 applications.
On November 29, 2021, we announced 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.
This change has now been completed. If your enterprise had applications that were not following this standard, you should have received four emails over the past few months describing how to update your applications.
How to solve redirect errors
If you did not receive the email or missed the communication, below you will find the steps to mitigate any issues.
- You can change the redirect URL in the Box Developer Console configuration tab for your application. If the URLs are static, then you can update the Developer console to add multiple URLs. If the URLs are dynamic, then update your application to use a static URL or use the state parameter.
- You can change the redirect URL used in your application code to strictly match the URL in the developer console.
For option #1, please use these steps:
- Login to Box as the application owner and navigate to the Box Developer Console
- Click on the application and navigate to the configuration tab
- Scroll down to the "OAuth 2.0 Redirect URI" section
- Update the current URL listed
For option #2, please modify your application code to replace the impacted used URLs to strictly match the URL in the Developer Console.
Updates
- Redirect URIs now force strict checking to match the URI passed in and URIs configured in the OAuth 2.0 application configuration
Where to get support
Should you have any issues or need further guidance, please post a request to our developer forum or file a ticket with Box Support.
Box UI Elements v15.0.0
released
Box UI Elements v15.0.0
released
15.0.0 (2022-05-16)
Bug Fixes & Features
This release fixes several bugs and adds new features. For a full list of changes, please see the release notes.
New Field Added to Sign Requests
New Field Added to Sign Requests
Box Sign request response objects now include a new field - content_type
. This field identifies the type of content expected for the type
of input
selected for the signer to complete.
Updates
- Added new field
content_type
to the sign request response object
Where to get support
Should you have any issues or need further guidance, please post a request to our developer forum.