Instruction
Difficulty level:
Beheer > Integraties > Box.com
Setting up the Box.com integration: steps on the Box and i-Reserve side
The Box.com integration needs configuration on two sides: first a JWT app in the Box Developer Console (and authorization in the Box Admin Console), then the integration itself in i-Reserve.
1. On the Box side
1.1 Create the JWT app
- Open the Box Developer Console and create an app with Server Authentication (with JWT).
- Generate a key pair: download the private key (PEM) and note the public key id and the passphrase.
- Note the client id and the client secret.
1.2 Authorize the app in the Admin Console
- Give the app the required scopes, including: create/read sign requests, upload/read files, read folders and manage webhooks (Box Sign bundle).
- Authorize the app in the Box Admin Console (Apps → Custom Apps Manager → authorize on the client id).
- Note the Enterprise ID (Admin Console → Account & Billing).
The webhook on the Box folder is created automatically by i-Reserve on a successful connection.
2. On the i-Reserve side
Go to Administration → Integrations and add a Box.com integration.
2.1 Authentication screen
| Field | What to enter |
|---|---|
| Client ID / Client secret | From the JWT app in the Box Developer Console. |
| Public key id | The id of the generated key pair. |
| Private key | The RSA private key in PEM format (multiple lines). |
| Passphrase | The passphrase protecting the private key. |
| Enterprise ID | The Box Enterprise ID. |
Click Request authentication: i-Reserve fetches a JWT token, shows the connected Box user and creates the i-Reserve folder + webhook.
2.2 Configuration screen
| Field | What to enter |
|---|---|
| As user | (Optional) The Box user the sign requests are created as. |
| Folder name | The name of the Box folder where sign requests/documents are stored. |
| Redirect URL | (Optional) The URL the customer is redirected to after signing. |
| Final copy recipient | (Optional) E-mail address that receives the signed final copy. |
| Order templates | The PDF templates generated and sent on “request signature”. |
| Order field for sign-request id | The order field that stores the Box sign-request id (crucial for the webhook link). |
2.3 Activate
Save and set the integration to active. Test by moving an order to the “request signature” status and checking that the sign request reaches the customer and the webhook reports the status back.
Without selected order templates no sign request is created on "request signature" (silent no-op). So select at least one PDF template and set the order field for the sign-request id.
The private key must be pasted exactly as PEM (multiple lines) and the app must be authorized in the Box Admin Console; otherwise JWT authentication fails. The webhook URL Box calls back must be publicly reachable.
