Documents

Seal a document

If you prefer to send the document manually, use this method to seal it. Do not use it if you send the document automatically or use send document. Sealing can only be performed on documents with status draft; a document created from a file has status importing until the file is processed, and sealing it before then returns 400, so poll get document status until it reports draft. Sealing returns individual access and signing links for each recipient; use send to recipients to release the document to recipients in batches. If the document was created with the self-sign option it is also self-signed by the authenticated or specified user before sealing.

Sealing finishes in the background once the document PDF has been generated, and the document stays in draft until then: poll get document status until it reports sealed before you send to recipients or create a reminder.

The optional User-Agent and CLIENT_IP headers specify the client device information and IP address recorded for the seal.

post/v1/documents/{id}/seal

Request

  • Base URL: https://api.getaccept.com
  • URL: https://api.getaccept.com/v1/documents/{id}/seal
  • Auth: HTTP bearer

Path parameters

idstring required

Id of the document.

Request body

sender_idstring

Id of a user of the entity who may send documents. Send document sends the document from this user and makes them its owner; send and seal both self-sign the document as this user when it was created with the self-sign option.

sender_emailstring

Email address of a user of the entity who may send documents, an alternative to sender_id that wins when both are set. Send document sends the document from this user and makes them its owner; send and seal both self-sign the document as this user when it was created with the self-sign option.

Response

The request succeeded.

Changes

No recorded changes to this operation across all 1 revision of this API.