Skip to navigation
API referencePost Processing Function Group

Rules for Exporting Authoritative Copy Envelopes

View as Markdown

This page describes functionality for the older eSignature SOAP API. See Authoritative copies for more information on this topic in the more actively-supported eSignature REST API documentation.

API user specific rules

  • The envelope ID passed to the API must be valid.
  • The envelope ID passed to the API must be in the Authoritative Copy status in Docusign.
  • The user and account must be configured properly by Docusign in order to enable this API.

Rules for Exceptions thrown by the ExportAuthoritativeCopy API

  • Envelope_Does_Not_Exist – invalid envelope ID passed.
  • User_Lacks_Permissions - The user making the API calls must have permissions to export Authoritative Copy Documents.
  • Envelope_AC_Export_Completed – the envelope being requested has already been exported from Docusign.
  • Envelope_AC_Export_Not_AC_Copy – the envelope being requested is not an Authoritative Copy.

Rules for Exceptions thrown by the AcknowledgeAuthoritativeCopyExport API

  • Envelope_Does_Not_Exist – invalid envelope ID passed.
  • User_Lacks_Permissions - The user making the API calls must have permissions to export Authoritative Copy Documents.
  • Envelope_AC_Export_Invalid_Status – envelope is not in the valid export status.
  • Envelope_AC_Export_Invalid_TransID – transaction ID passed is invalid.

Rules for return value of the AcknowledgeAuthoritativeCopyExport API

  • AuthoritativeCopyExportSuccess – True if export was successfully completed.
  • ExportKey – key to decrypt the Rijndael encrypted documents. This key is only provided if AuthoritativeCopyExportSuccess is true. Encryption mode is CBC. Encryption padding is PKCS7.