How a signature request works
Every integration follows the same path:- Pick a document. It can be a plain file that needs preparation, a file that already carries signature tags, or a template you built in the Box web app. See document types.
- Create the request. Name the file, a destination folder, and at least one signer, along with any options you need. See create a Box Sign request.
- Get the request to the signers. Let Box email them, send the link yourself, or embed the signing client in your app. See deliver the request to signers.
- Track it to completion. Requests are asynchronous, so watch the request status or subscribe to webhooks.
.pdf and the signing log in
the destination folder.
Where to start
If you are new to Box Sign, set up your account and scopes, then send one request end to end with the quick start. If you are scoping an integration, the endpoints page shows the whole API surface on one screen.What you can configure
Most of what makes a signature request specific to your use case is set when you create it:- Multiple signers and signing order for approvals and sequential signing
- Signer verification for smart card, SMS, login, or password checks
- In-person signing when the signer is standing next to the requester
- 21 CFR Part 11 requests for GxP workflows