Skip to content

Integrating Box Sign

Auth: OAuth 2.0 · Partner program: not required · Setup time: about 20 minutes · Last verified: 2026-05-20

Box-native e-signature embedded in Box Business+ workflows. The same Box OAuth credentials that read files can also drive the Sign API.

OAuth 2.0 Authorization Code grant via Box. Authorize at https://developer.box.com/guides/authentication/oauth2/; exchange at https://api.box.com/oauth2/token.

  1. Create a Box Custom App at the Box Developer Console.
  2. Enable App Access Only or User Authentication (OAuth 2.0) depending on integration mode.
  3. Grant scope Write all files and folders stored in Box + Manage signature requests.
  4. Add <base-url>/auth/docsign/box-sign/callback to the redirect URIs.

Set the client credentials as the adapter’s config — on the platform’s page in the admin UI (/platforms/docsign/box-sign), or:

Terminal window
curl -X POST "$INTEGRATION_SERVER_URL/admin/platforms/docsign/box-sign/enable" \
-H "X-Admin-Secret: $ADMIN_SECRET" -H "Content-Type: application/json" \
-d '{"config":{"clientId":"...","clientSecret":"...","redirectUri":"<base-url>/auth/docsign/box-sign/callback"}}'

These are adapter settings, not environment variables: nothing reads a BOX_SIGN_CLIENT_ID from .env. See OAuth adapter credentials.

Box signs webhook deliveries with HMAC-SHA1 of <timestamp><body> using the webhook key. The signature ships in X-Box-Signature-Primary (base64). Key rotation supported via X-Box-Signature-Secondary.

  • Document content — this adapter does not expose Box file bodies
  • Signature images

This adapter covers only the sign-request subset of the Box API; it does not read or manage Box files.