Box Sign brings the full Box Sign web app experience to your application
through the API. Your app chooses the document, decides who signs it and in
what order, and receives the signed file and a signing log back in a Box
folder.
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.
When everyone has signed, Box stores the signed .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.
Most of what makes a signature request specific to your use case is set when
you create it:
Language, expiration, and redirect options are covered on the
create a Box Sign request page.
Last modified on September 18, 2026
