Cancel a Box Sign request

A Box Sign request that has not yet been signed or declined can be cancelled using the cancel Box Sign request endpoint. Any outstanding signers cannot sign the document. Only the requester (the user who created the request) can cancel it. You can’t cancel a request that was declined, fully signed, or where the document is still converting.

Cancel a request

curl -i -X POST "https://api.box.com/2.0/sign_requests/<SIGN_REQUEST_ID>/cancel" \
     -H "authorization: Bearer <ACCESS_TOKEN>"

await client.signRequests.cancelSignRequest(createdSignRequest.id!);

client.sign_requests.cancel_sign_request(created_sign_request.id)

await client.SignRequests.CancelSignRequestAsync(signRequestId: NullableUtils.Unwrap(createdSignRequest.Id));

try await client.signRequests.cancelSignRequest(signRequestId: createdSignRequest.id!)

client.getSignRequests().cancelSignRequest(createdSignRequest.getId())

BoxSignRequest signRequest = new BoxSignRequest(api, id);
BoxSignRequest.Info signRequestInfo = signRequest.getInfo();

signRequestInfo.cancel();

sign_request = client.sign_request(sign_request_id='12345')
cancelled_sign_request = sign_request.cancel()
print(f'Cancelled Sign Request status is {cancelled_sign_request.status}')

BoxSignRequest cancelledSignRequest = await client.SignRequestsManager.CancelSignRequestAsync("12345");

const signRequest = await client.signRequests.cancelById({
	sign_request_id: 12345,
});
console.log(`Sign request id ${sr.id} cancelled`);

Provide a cancellation reason

The request body accepts a reason field describing why the request was cancelled. The reason can be up to 255 characters.

cURL

curl -i -X POST "https://api.box.com/2.0/sign_requests/<SIGN_REQUEST_ID>/cancel" \
     -H "authorization: Bearer <ACCESS_TOKEN>" \
     -H "content-type: application/json" \
     -d '{ "reason": "Project cancelled" }'

Whether you need to send a reason depends on the enterprise settings of the requester:

Reason enforcement for sender actions is off (default): The request body and the reason field are optional.
Reason enforcement for sender actions is on: The reason field is required and can’t be empty or contain only whitespace. If the reason is missing, empty, or longer than 255 characters, the API returns a 400 error and the request isn’t cancelled.

Box checks the setting when you cancel the request, so the requirement also applies to requests sent before the admin turned on enforcement. Reason enforcement is available on Business plans and above.

Not every SDK accepts a request body for the cancel method. If your SDK doesn’t, call the endpoint directly to send a cancellation reason.

Control signer notifications

Signer notifications are configured per signer when the request is created, not when it is cancelled, so the cancel endpoint takes no notification parameters. To turn the default emails off and send your own, see How signers get the request.

Last modified on October 19, 2026

Getting started

Applications & integrations

Identity & access

Using the API

Troubleshooting

Content

Collaboration

Metadata & search

Events & webhooks

Users

Intelligent workflow

E-signatures

Security & compliance

Cancel a Box Sign request

Cancel a request

Provide a cancellation reason

Control signer notifications

​Cancel a request

​Provide a cancellation reason

​Control signer notifications

Cancel a request

Provide a cancellation reason

Control signer notifications