=begin #DocuSign REST API #The DocuSign REST API provides you with a powerful, convenient, and simple Web services API for interacting with DocuSign. OpenAPI spec version: v2 Contact: devcenter@docusign.com Generated by: https://github.com/swagger-api/swagger-codegen.git =end require 'spec_helper' require 'json' # Unit tests for SwaggerClient::EnvelopesApi # Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) # Please update as you see appropriate describe 'EnvelopesApi' do before do # run before each test @instance = SwaggerClient::EnvelopesApi.new end after do # run after each test end describe 'test an instance of EnvelopesApi' do it 'should create an instact of EnvelopesApi' do expect(@instance).to be_instance_of(SwaggerClient::EnvelopesApi) end end # unit tests for apply_template # Adds templates to an envelope. # Adds templates to the specified envelope. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [DocumentTemplateList] :document_template_list # @return [DocumentTemplateList] describe 'apply_template test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for apply_template_to_document # Adds templates to a document in an envelope. # Adds templates to a document in the specified envelope. # @param account_id The external account number (int) or account ID Guid. # @param document_id The ID of the document being accessed. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [DocumentTemplateList] :document_template_list # @return [DocumentTemplateList] describe 'apply_template_to_document test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for create_chunked_upload # Initiate a new ChunkedUpload. # # @param account_id The external account number (int) or account ID Guid. # @param [Hash] opts the optional parameters # @option opts [ChunkedUploadRequest] :chunked_upload_request # @return [ChunkedUploadResponse] describe 'create_chunked_upload test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for create_console_view # Returns a URL to the authentication view UI. # Returns a URL that allows you to embed the authentication view of the DocuSign UI in your applications. # @param account_id The external account number (int) or account ID Guid. # @param [Hash] opts the optional parameters # @option opts [ConsoleViewRequest] :console_view_request # @return [ViewUrl] describe 'create_console_view test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for create_correct_view # Returns a URL to the envelope correction UI. # Returns a URL that allows you to embed the envelope correction view of the DocuSign UI in your applications. Important: iFrames should not be used for embedded operations on mobile devices due to screen space issues. For iOS devices DocuSign recommends using a WebView. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [CorrectViewRequest] :correct_view_request # @return [ViewUrl] describe 'create_correct_view test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for create_custom_fields # Updates envelope custom fields for an envelope. # Updates the envelope custom fields for draft and in-process envelopes. Each custom field used in an envelope must have a unique name. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [CustomFields] :custom_fields # @return [CustomFields] describe 'create_custom_fields test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for create_document_fields # Creates custom document fields in an existing envelope document. # Creates custom document fields in an existing envelope document. # @param account_id The external account number (int) or account ID Guid. # @param document_id The ID of the document being accessed. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [DocumentFieldsInformation] :document_fields_information # @return [DocumentFieldsInformation] describe 'create_document_fields test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for create_edit_view # Returns a URL to the edit view UI. # Returns a URL that allows you to embed the edit view of the DocuSign UI in your applications. This is a one-time use login token that allows the user to be placed into the DocuSign editing view. Upon sending completion, the user is returned to the return URL provided by the API application. Important: iFrames should not be used for embedded operations on mobile devices due to screen space issues. For iOS devices DocuSign recommends using a WebView. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [ReturnUrlRequest] :return_url_request # @return [ViewUrl] describe 'create_edit_view test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for create_email_settings # Adds email setting overrides to an envelope. # Adds email override settings, changing the email address to reply to an email address, name, or the BCC for email archive information, for the envelope. Note that adding email settings will only affect email communications that occur after the addition was made. ### Important: The BCC Email address feature is designed to provide a copy of all email communications for external archiving purposes. DocuSign recommends that envelopes sent using the BCC for Email Archive feature, including the BCC Email Override option, include additional signer authentication options. To send a copy of the envelope to a recipient who does not need to sign, use a Carbon Copies or Certified Deliveries Recipient Type. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [EmailSettings] :email_settings # @return [EmailSettings] describe 'create_email_settings test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for create_envelope # Creates an envelope. # Creates an envelope. Using this function you can: * Create an envelope and send it. * Create an envelope from an existing template and send it. In either case, you can choose to save the envelope as a draft envelope instead of sending it by setting the request’s `status` property to `created` instead of `sent`. ## Sending Envelopes Documents can be included with the Envelopes::create call itself or a template can include documents. Documents can be added by using a multi-part/form request or by using the `documentBase64` field of the [`document` object](#/definitions/document) ### Recipient Types An [`envelopeDefinition` object](#/definitions/envelopeDefinition) is used as the method’s body. Envelope recipients can be defined in the envelope or in templates. The `envelopeDefinition` object’s `recipients` field is an [`EnvelopeRecipients` resource object](#/definitions/EnvelopeRecipients). It includes arrays of the seven types of recipients defined by DocuSign: Recipient type | Object definition -------------- | ----------------- agent (can add name and email information for later recipients/signers) | [`agent`](#/definitions/agent) carbon copy (receives a copy of the documents) | [`carbonCopy`](#/definitions/carbonCopy) certified delivery (receives a copy of the documents and must acknowledge receipt) | [`certifiedDelivery`](#/definitions/certifiedDelivery) editor (can change recipients and document fields for later recipients/signers) | [`editor`](#/definitions/editor) in-person signer (“hosts” someone who signs in-person) | [`inPersonSigner`](#/definitions/inPersonSigner) intermediary (can add name and email information for some later recipients/signers.) | [`intermediary`](#/definitions/intermediary) signer (signs and/or updates document fields) | [`signer`](#/definitions/signer) Additional information about the different types of recipients is available from the [`EnvelopeRecipients` resource page](../../EnvelopeRecipients) and from the [Developer Center](https://www.docusign.com/developer-center/explore/features/recipients) ### Tabs Tabs (also referred to as `tags` and as `fields` in the web sending user interface), can be defined in the `envelopeDefinition`, in templates, by transforming PDF Form Fields, or by using Composite Templates (see below). Defining tabs: the `inPersonSigner`, and `signer` recipient objects include a `tabs` field. It is an [`EnvelopeTabs` resource object](#/definitions/EnvelopeTabs). It includes arrays of the 24 different tab types available. See the [`EnvelopeTabs` resource](../../EnvelopeTabs) for more information. ## Using Templates Envelopes use specific people or groups as recipients. Templates can specify a role, eg `account_manager.` When a template is used in an envelope, the roles must be replaced with specific people or groups. When you create an envelope using a `templateId`, the different recipient type objects within the [`EnvelopeRecipients` object](#/definitions/EnvelopeRecipients) are used to assign recipients to the template’s roles via the `roleName` property. The recipient objects can also override settings that were specified in the template, and set values for tab fields that were defined in the template. ### Message Lock When a template is added or applied to an envelope and the template has a locked email subject and message, that subject and message are used for the envelope and cannot be changed even if another locked template is subsequently added or applied to the envelope. The field `messageLock` is used to lock the email subject and message. If an email subject or message is entered before adding or applying a template with `messageLock` **true**, the email subject and message is overwritten with the locked email subject and message from the template. ## Envelope Status The status of sent envelopes can be determined through the DocuSign webhook system or by polling. Webhooks are highly recommended: they provide your application with the quickest updates when an envelope’s status changes. DocuSign limits polling to once every 15 minutes or less frequently. When a webhook is used, DocuSign calls your application, via the URL you provide, with a notification XML message. See the [Webhook recipe](https://www.docusign.com/developer-center/recipes/webhook-status) for examples and live demos of using webhooks. ## Webhook Options The two webhook options, *eventNotification* and *Connect* use the same notification mechanism and message formats. eventNotification is used to create a webhook for a specific envelope sent via the API. Connect webhooks can be used for any envelope sent from an account, from any user, from any client. ### eventNotification Webhooks The Envelopes::create method includes an optional [eventNotification object](#definition-eventNotification) that adds a webhook to the envelope. eventNotification webhooks are available for all DocuSign accounts with API access. ### Connect Webhooks Connect can be used to create a webhook for all envelopes sent by all users in an account, either through the API or via other DocuSign clients (web, mobile, etc). Connect configurations are independent of specific envelopes. A Connect configuration includes a filter that may be used to limit the webhook to specific users, envelope statuses, etc. Connect configurations may be created and managed using the [ConnectConfigurations resource](../../Connect/ConnectConfigurations). Configurations can also be created and managed from the Administration tool accessed by selecting “Go to Admin” from the menu next to your picture on the DocuSign web app. See the Integrations/Connect section of the Admin tool. For repeatability, and to minimize support questions, creating Connect configurations via the API is recommended, especially for ISVs. Connect is available for some DocuSign account types. Please contact DocuSign Sales for more information. ## Composite Templates The Composite Templates feature, like [compositing in film production](https://en.wikipedia.org/wiki/Compositing), enables you to *overlay* document, recipient, and tab definitions from multiple sources, including PDF Form Field definitions, templates defined on the server, and more. Each Composite Template consists of optional elements: server templates, inline templates, PDF Metadata templates, and documents. * The Composite Template ID is an optional element used to identify the composite template. It is used as a reference when adding document object information via a multi-part HTTP message. If used, the document content-disposition must include the `compositeTemplateId` to which the document should be added. If `compositeTemplateId` is not specified in the content-disposition, the document is applied based on the `documentId` only. If no document object is specified, the composite template inherits the first document. * Server Templates are server-side templates stored on the DocuSign platform. If supplied, they are overlaid into the envelope in the order of their Sequence value. * Inline Templates provide a container to add documents, recipients, tabs, and custom fields. If inline templates are supplied, they are overlaid into the envelope in the order of their Sequence value. * Document objects are optional structures that provide a container to pass in a document or form. If this object is not included, the composite template inherits the *first* document it finds from a server template or inline template, starting with the lowest sequence value. PDF Form objects are only transformed from the document object. DocuSign does not derive PDF form properties from server templates or inline templates. To instruct DocuSign to transform fields from the PDF form, set `transformPdfFields` to \"true\" for the document. See the Transform PDF Fields section for more information about process. * PDF Metadata Templates provide a container to embed design-time template information into a PDF document. DocuSign uses this information when processing the Envelope. This convention allows the document to carry the signing instructions with it, so that less information needs to be provided at run-time through an inline template or synchronized with an external structure like a server template. PDF Metadata templates are stored in the Metadata layer of a PDF in accordance with Acrobat's XMP specification. DocuSign will only find PDF Metadata templates inside documents passed in the Document object (see below). If supplied, the PDF metadata template will be overlaid into the envelope in the order of its Sequence value. ### Compositing the definitions Each Composite Template adds a new document and templates overlay into the envelope. For each Composite Template these rules are applied: * Templates are overlaid in the order of their Sequence value. * If Document is not passed into the Composite Template’s `document` field, the *first* template’s document (based on the template’s Sequence value) is used. * Last in wins in all cases except for the document (i.e. envelope information, recipient information, secure field information). There is no special casing. For example, if you want higher security on a tab, then that needs to be specified in a later template (by sequence number) then where the tab is included. If you want higher security on a role recipient, then it needs to be in a later template then where that role recipient is specified. * Recipient matching is based on Recipient Role and Routing Order. If there are matches, the recipient information is merged together. A final pass is done on all Composite Templates, after all template overlays have been applied, to collapse recipients with the same email, username and routing order. This prevents having the same recipients at the same routing order. * If you specify in a template that a recipient is locked, once that recipient is overlaid the recipient attributes can no longer be changed. The only items that can be changed for the recipient in this case are the email, username, access code and IDCheckInformationInput. * Tab matching is based on Tab Labels, Tab Types and Documents. If a Tab Label matches but the Document is not supplied, the Tab is overlaid for all the Documents. For example, if you have a simple inline template with only one tab in it with a label and a value, the Signature, Initial, Company, Envelope ID, User Name tabs will only be matched and collapsed if they fall in the exact same X and Y locations. * roleName and tabLabel matching is case sensitive. * The defaultRecipient field enables you to specify which recipient the generated tabs from a PDF form are mapped to. You can also set PDF form generated tabs to a recipient other than the DefaultRecipient by specifying the mapping of the tab label that is created to one of the template recipients. * You can use tabLabel wild carding to map a series of tabs from the PDF form. To use this you must end a tab label with “\\*” and then the system matches tabs that start with the label. * If no DefaultRecipient is specified, tabs must be explicitly mapped to recipients in order to be generated from the form. Unmapped form objects will not be generated into their DocuSign equivalents. (In the case of Signature/Initials, the tabs will be disregarded entirely; in the case of pdf text fields, the field data will be flattened on the Envelope document, but there will not be a corresponding DocuSign data tab.) ### Including the Document Content for Composite Templates Document content can be supplied inline, using the `documentBase64` or can be included in a multi-part HTTP message. If a multi-part message is used and there are multiple Composite Templates, the document content-disposition can include the `compositeTemplateId` to which the document should be added. Using the `compositeTemplateId` sets which documents are associated with particular composite templates. An example of this usage is: ``` --5cd3320a-5aac-4453-b3a4-cbb52a4cba5d Content-Type: application/pdf Content-Disposition: file; filename=\"eula.pdf\"; documentId=1; compositeTemplateId=\"1\" Content-Transfer-Encoding: base64 ``` ### PDF Form Field Transformation Only the following PDF Form FieldTypes will be transformed to DocuSign tabs: CheckBox, DateTime, ListBox, Numeric, Password, Radio, Signature, and Text Field Properties that will be transformed: Read Only, Required, Max Length, Positions, and Initial Data. When transforming a *PDF Form Digital Signature Field,* the following rules are used: If the PDF Field Name Contains | Then the DocuSign Tab Will be ------- | -------- DocuSignSignHere or eSignSignHere | Signature DocuSignSignHereOptional or eSignSignHereOptional | Optional Signature DocuSignInitialHere or eSignInitialHere | Initials DocuSignInitialHereOptional or eSignInitialHereOptional | Optional Initials Any other PDF Form Digital Signature Field will be transformed to a DocuSign Signature tab When transforming *PDF Form Text Fields,* the following rules are used: If the PDF Field Name Contains | Then the DocuSign Tab Will be ------- | -------- DocuSignSignHere or eSignSignHere | Signature DocuSignSignHereOptional or eSignSignHereOptional | Optional Signature DocuSignInitialHere or eSignInitialHere | Initials DocuSignInitialHereOptional or eSignInitialHereOptional | Optional Initials DocuSignEnvelopeID or eSignEnvelopeID | EnvelopeID DocuSignCompany or eSignCompany | Company DocuSignDateSigned or eSignDateSigned | Date Signed DocuSignTitle or eSignTitle | Title DocuSignFullName or eSignFullName | Full Name DocuSignSignerAttachmentOptional or eSignSignerAttachmentOptional | Optional Signer Attachment Any other PDF Form Text Field will be transformed to a DocuSign data (text) tab. PDF Form Field Names that include “DocuSignIgnoreTransform” or “eSignIgnoreTransform” will not be transformed. PDF Form Date fields will be transformed to Date Signed fields if their name includes DocuSignDateSigned or eSignDateSigned. ## Template Email Subject Merge Fields This feature enables you to insert recipient name and email address merge fields into the email subject line when creating or sending from a template. The merge fields, based on the recipient’s `roleName`, are added to the `emailSubject` when the template is created or when the template is used to create an envelope. After a template sender adds the name and email information for the recipient and sends the envelope, the recipient information is automatically merged into the appropriate fields in the email subject line. Both the sender and the recipients will see the information in the email subject line for any emails associated with the template. This provides an easy way for senders to organize their envelope emails without having to open an envelope to check the recipient. If merging the recipient information into the subject line causes the subject line to exceed 100 characters, then any characters over the 100 character limit are not included in the subject line. For cases where the recipient name or email is expected to be long, you should consider placing the merge field at the start of the email subject. * To add a recipient’s name in the subject line add the following text in the `emailSubject` when creating the template or when sending an envelope from a template: [[<roleName>_UserName]] Example: `\"emailSubject\":\"[[Signer 1_UserName]], Please sign this NDA\",` * To add a recipient’s email address in the subject line add the following text in the emailSubject when creating the template or when sending an envelope from a template: [[<roleName>_Email]] Example: `\"emailSubject\":\"[[Signer 1_Email]], Please sign this NDA\",` In both cases the <roleName> is the recipient’s `roleName` in the template. For cases where another recipient (such as an Agent, Editor, or Intermediary recipient) is entering the name and email information for the recipient included in the email subject, then [[<roleName>_UserName]] or [[<roleName>_Email]] is shown in the email subject. ## Branding an envelope The following rules are used to determine the `brandId` used in an envelope: * If a `brandId` is specified in the envelope/template and that brandId is available to the account, that brand is used in the envelope. * If more than one template is used in an envelope and more than one `brandId` is specified, the first `brandId` specified is used throughout the envelope. * In cases where no brand is specified and the sender belongs to a Group; if there is only one brand associated with the Group, then that brand is used in the envelope. Otherwise, the account’s default signing brand is used. * For envelopes that do not meet any of the previous criteria, the account’s default signing brand is used for the envelope. ## BCC Email address feature The BCC Email address feature is designed to provide a copy of all email communications for external archiving purposes. DocuSign recommends that envelopes sent using the BCC for Email Archive feature, including the BCC Email Override option, include additional signer authentication options. To send a copy of the envelope to a recipient who does not need to sign, don’t use the BCC Email field. Use a Carbon Copy or Certified Delivery Recipient type. ## Merge Recipient Roles for Draft Envelopes When an envelope with multiple templates is sent, the recipients from the templates are merged according to the template roles, and empty recipients are removed. When creating an envelope with multiple templates, but not sending it (keeping it in a created state), duplicate recipients are not merged, which could cause leave duplicate recipients in the envelope. To prevent this, the query parameter `merge_roles_on_draft` should be added when posting a draft envelope (status=created) with multiple templates. Doing this will merge template roles and remove empty recipients. ###### Note: DocuSign recommends that the `merge_roles_on_draft` query parameter be used anytime you are creating an envelope with multiple templates and keeping it in draft (created) status. # @param account_id The external account number (int) or account ID Guid. # @param [Hash] opts the optional parameters # @option opts [String] :cdse_mode # @option opts [String] :completed_documents_only If set to true then we want to set the sourceEnvelopeId to indicate that this is a\"forward\" envelope action # @option opts [String] :merge_roles_on_draft When set to **true**, merges template roles and remove empty recipients when you create an envelope with multiple templates. # @option opts [EnvelopeDefinition] :envelope_definition # @return [EnvelopeSummary] describe 'create_envelope test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for create_lock # Lock an envelope. # Locks the specified envelope, and sets the time until the lock expires, to prevent other users or recipients from accessing and changing the envelope. ###### Note: Users must have envelope locking capability enabled to use this function (userSetting `canLockEnvelopes` must be set to true for the user). # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [LockRequest] :lock_request # @return [LockInformation] describe 'create_lock test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for create_recipient # Adds one or more recipients to an envelope. # Adds one or more recipients to an envelope. For an in process envelope, one that has been sent and has not been completed or voided, an email is sent to a new recipient when they are reached in the routing order. If the new recipient's routing order is before or the same as the envelope's next recipient, an email is only sent if the optional `resend_envelope` query string is set to **true**. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :resend_envelope When set to **true**, resends the envelope if the new recipient's routing order is before or the same as the envelope’s next recipient. # @option opts [Recipients] :recipients # @return [Recipients] describe 'create_recipient test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for create_recipient_view # Returns a URL to the recipient view UI. # Returns a URL that allows you to embed the recipient view of the DocuSign UI in your applications. This call cannot be used to view draft envelopes, since those envelopes have not been sent. Important: iFrames should not be used for embedded operations on mobile devices due to screen space issues. For iOS devices DocuSign recommends using a WebView. An entry is added into the Security Level section of the DocuSign Certificate of Completion that reflects the `securityDomain` and `authenticationMethod` properties used to verify the user identity. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [RecipientViewRequest] :recipient_view_request # @return [ViewUrl] describe 'create_recipient_view test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for create_sender_view # Returns a URL to the sender view UI. # Returns a URL that allows you to embed the sender view of the DocuSign UI in your applications. This is a one-time use login token that allows the user to be placed into the DocuSign sending view. Upon sending completion, the user is returned to the return URL provided by the API application. Important: iFrames should not be used for embedded operations on mobile devices due to screen space issues. For iOS devices DocuSign recommends using a WebView. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [ReturnUrlRequest] :return_url_request # @return [ViewUrl] describe 'create_sender_view test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for create_tabs # Adds tabs for a recipient. # Adds one or more tabs for a recipient. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param recipient_id The ID of the recipient being accessed. # @param [Hash] opts the optional parameters # @option opts [Tabs] :tabs # @return [Tabs] describe 'create_tabs test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for create_view_link # Reserved: Returns a URL to the secure link view UI. # Reserved: Returns a URL that allows you to embed the secure link view of the DocuSign UI in your applications. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [ViewLinkRequest] :view_link_request # @return [ViewUrl] describe 'create_view_link test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for delete_attachments # Delete one or more attachments from a DRAFT envelope. # # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [EnvelopeAttachmentsRequest] :envelope_attachments_request # @return [EnvelopeAttachmentsResult] describe 'delete_attachments test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for delete_chunked_upload # Delete an existing ChunkedUpload. # # @param account_id The external account number (int) or account ID Guid. # @param chunked_upload_id # @param [Hash] opts the optional parameters # @return [ChunkedUploadResponse] describe 'delete_chunked_upload test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for delete_custom_fields # Deletes envelope custom fields for draft and in-process envelopes. # Deletes envelope custom fields for draft and in-process envelopes. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [CustomFields] :custom_fields # @return [CustomFields] describe 'delete_custom_fields test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for delete_document_fields # Deletes custom document fields from an existing envelope document. # Deletes custom document fields from an existing envelope document. # @param account_id The external account number (int) or account ID Guid. # @param document_id The ID of the document being accessed. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [DocumentFieldsInformation] :document_fields_information # @return [DocumentFieldsInformation] describe 'delete_document_fields test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for delete_document_page # Deletes a page from a document in an envelope. # Deletes a page from a document in an envelope based on the page number. # @param account_id The external account number (int) or account ID Guid. # @param document_id The ID of the document being accessed. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param page_number The page number being accessed. # @param [Hash] opts the optional parameters # @return [nil] describe 'delete_document_page test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for delete_documents # Deletes documents from a draft envelope. # Deletes one or more documents from an existing draft envelope. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [EnvelopeDefinition] :envelope_definition # @return [EnvelopeDocumentsResult] describe 'delete_documents test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for delete_email_settings # Deletes the email setting overrides for an envelope. # Deletes all existing email override settings for the envelope. If you want to delete an individual email override setting, use the PUT and set the value to an empty string. Note that deleting email settings will only affect email communications that occur after the deletion and the normal account email settings are used for future email communications. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @return [EmailSettings] describe 'delete_email_settings test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for delete_lock # Deletes an envelope lock. # Deletes the lock from the specified envelope. The `X-DocuSign-Edit` header must be included in the request. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @return [LockInformation] describe 'delete_lock test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for delete_recipient # Deletes a recipient from an envelope. # Deletes the specified recipient file from the specified envelope. This cannot be used if the envelope has been sent. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param recipient_id The ID of the recipient being accessed. # @param [Hash] opts the optional parameters # @return [Recipients] describe 'delete_recipient test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for delete_recipients # Deletes recipients from an envelope. # Deletes one or more recipients from a draft or sent envelope. Recipients to be deleted are listed in the request, with the `recipientId` being used as the key for deleting recipients. If the envelope is `In Process`, meaning that it has been sent and has not been completed or voided, recipients that have completed their actions cannot be deleted. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [Recipients] :recipients # @return [Recipients] describe 'delete_recipients test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for delete_tabs # Deletes the tabs associated with a recipient. # Deletes one or more tabs associated with a recipient in a draft envelope. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param recipient_id The ID of the recipient being accessed. # @param [Hash] opts the optional parameters # @option opts [Tabs] :tabs # @return [Tabs] describe 'delete_tabs test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for delete_templates_from_document # Deletes a template from a document in an existing envelope. # Deletes the specified template from a document in an existing envelope. # @param account_id The external account number (int) or account ID Guid. # @param document_id The ID of the document being accessed. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param template_id The ID of the template being accessed. # @param [Hash] opts the optional parameters # @return [nil] describe 'delete_templates_from_document test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for delete_view_link # Reserved: Expires a secure view link. # Reserved: Expires a secure view link # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @return [nil] describe 'delete_view_link test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_attachment # Retrieves an attachment from the envelope. # # @param account_id The external account number (int) or account ID Guid. # @param attachment_id # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @return [nil] describe 'get_attachment test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_attachments # Returns a list of attachments associated with the specified envelope # # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @return [EnvelopeAttachmentsResult] describe 'get_attachments test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_chunked_upload # Retrieves the current metadata of a ChunkedUpload. # # @param account_id The external account number (int) or account ID Guid. # @param chunked_upload_id # @param [Hash] opts the optional parameters # @option opts [String] :include # @return [ChunkedUploadResponse] describe 'get_chunked_upload test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_consumer_disclosure # Reserved: Gets the Electronic Record and Signature Disclosure associated with the account. # Reserved: Retrieves the Electronic Record and Signature Disclosure, with HTML formatting, associated with the account. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param lang_code The simple type enumeration the language used in the response. The supported languages, with the language value shown in parenthesis, are:Arabic (ar), Bulgarian (bg), Czech (cs), Chinese Simplified (zh_CN), Chinese Traditional (zh_TW), Croatian (hr), Danish (da), Dutch (nl), English US (en), English UK (en_GB), Estonian (et), Farsi (fa), Finnish (fi), French (fr), French Canada (fr_CA), German (de), Greek (el), Hebrew (he), Hindi (hi), Hungarian (hu), Bahasa Indonesia (id), Italian (it), Japanese (ja), Korean (ko), Latvian (lv), Lithuanian (lt), Bahasa Melayu (ms), Norwegian (no), Polish (pl), Portuguese (pt), Portuguese Brazil (pt_BR), Romanian (ro), Russian (ru), Serbian (sr), Slovak (sk), Slovenian (sl), Spanish (es),Spanish Latin America (es_MX), Swedish (sv), Thai (th), Turkish (tr), Ukrainian (uk) and Vietnamese (vi). Additionally, the value can be set to �browser� to automatically detect the browser language being used by the viewer and display the disclosure in that language. # @param recipient_id The ID of the recipient being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :lang_code2 # @return [ConsumerDisclosure] describe 'get_consumer_disclosure test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_consumer_disclosure_default # Gets the Electronic Record and Signature Disclosure associated with the account. # Retrieves the Electronic Record and Signature Disclosure, with html formatting, associated with the account. You can use an optional query string to set the language for the disclosure. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param recipient_id The ID of the recipient being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :lang_code # @return [ConsumerDisclosure] describe 'get_consumer_disclosure_default test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_document # Gets a document from an envelope. # Retrieves the specified document from the envelope. If the account has the Highlight Data Changes feature enabled, there is an option to request that any changes in the envelope be highlighted. You can also use this method to retrieve a PDF containing the combined content of all documents and the certificate. If the account has the Highlight Data Changes feature enabled, there is an option to request that any changes in the envelope be highlighted. To retrieve the combined content replace the `{documentId}` parameter in the endpoint with `combined`. /accounts/{accountId}/envelopes/{envelopeId}/documents/combined # @param account_id The external account number (int) or account ID Guid. # @param document_id The ID of the document being accessed. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :certificate When set to **false**, the envelope signing certificate is removed from the download. # @option opts [String] :encoding # @option opts [String] :encrypt When set to **true**, the PDF bytes returned in the response are encrypted for all the key managers configured on your DocuSign account. The documents can be decrypted with the KeyManager Decrypt Document API. # @option opts [String] :language Specifies the language for the Certificate of Completion in the response. The supported languages, with the language value shown in parenthesis, are: Chinese Simplified (zh_CN), , Chinese Traditional (zh_TW), Dutch (nl), English US (en), French (fr), German (de), Italian (it), Japanese (ja), Korean (ko), Portuguese (pt), Portuguese (Brazil) (pt_BR), Russian (ru), Spanish (es). # @option opts [String] :recipient_id # @option opts [String] :show_changes When set to **true**, any changed fields for the returned PDF are highlighted in yellow and optional signatures or initials outlined in red. # @option opts [String] :watermark When set to **true**, the account has the watermark feature enabled, and the envelope is not complete, the watermark for the account is added to the PDF documents. This option can remove the watermark. # @return [File] describe 'get_document test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_document_page_image # Gets a page image from an envelope for display. # Retrieves a page image for display from the specified envelope. # @param account_id The external account number (int) or account ID Guid. # @param document_id The ID of the document being accessed. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param page_number The page number being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :dpi Sets the dpi for the image. # @option opts [String] :max_height Sets the maximum height for the page image in pixels. The dpi is recalculated based on this setting. # @option opts [String] :max_width Sets the maximum width for the page image in pixels. The dpi is recalculated based on this setting. # @option opts [String] :show_changes # @return [File] describe 'get_document_page_image test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_email_settings # Gets the email setting overrides for an envelope. # Retrieves the email override settings for the specified envelope. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @return [EmailSettings] describe 'get_email_settings test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_envelope # Gets the status of a envelope. # Retrieves the overall status for the specified envelope. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :advanced_update When true, envelope information can be added or modified. # @option opts [String] :include # @return [Envelope] describe 'get_envelope test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_form_data # Returns envelope form data for an existing envelope. # # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @return [EnvelopeFormData] describe 'get_form_data test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_lock # Gets envelope lock information. # Retrieves general information about the envelope lock. If the call is made by the locked by user and the request has the same integrator key as original, then the `X-DocuSign-Edit` header and additional lock information is included in the response. This allows users to recover a lost editing session token and the `X-DocuSign-Edit` header. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @return [LockInformation] describe 'get_lock test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_notification_settings # Gets envelope notification information. # Retrieves the envelope notification, reminders and expirations, information for an existing envelope. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @return [Notification] describe 'get_notification_settings test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_recipient_document_visibility # Returns document visibility for the recipients # # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param recipient_id The ID of the recipient being accessed. # @param [Hash] opts the optional parameters # @return [DocumentVisibilityList] describe 'get_recipient_document_visibility test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_recipient_initials_image # Gets the initials image for a user. # Retrieves the initials image for the specified user. The image is returned in the same format as it was uploaded. In the request you can specify if the chrome (the added line and identifier around the initial image) is returned with the image. The userId specified in the endpoint must match the authenticated user's user id and the user must be a member of the account. The `signatureIdOrName` paramter accepts signature ID or signature name. DocuSign recommends you use signature ID (`signatureId`), since some names contain characters that do not properly URL encode. If you use the user name, it is likely that the name includes spaces and you might need to URL encode the name before using it in the endpoint. For example: \"Bob Smith\" to \"Bob%20Smith\" Older envelopes might only contain chromed images. If getting the non-chromed image fails, try getting the chromed image. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param recipient_id The ID of the recipient being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :include_chrome The added line and identifier around the initial image. Note: Older envelopes might only have chromed images. If getting the non-chromed image fails, try getting the chromed image. # @return [File] describe 'get_recipient_initials_image test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_recipient_signature # Gets signature information for a signer or sign-in-person recipient. # Retrieves signature information for a signer or sign-in-person recipient. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param recipient_id The ID of the recipient being accessed. # @param [Hash] opts the optional parameters # @return [UserSignature] describe 'get_recipient_signature test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_recipient_signature_image # Retrieve signature image information for a signer/sign-in-person recipient. # Retrieves the specified user signature image. The image is returned in the same format as uploaded. In the request you can specify if the chrome (the added line and identifier around the initial image) is returned with the image. The userId specified in the endpoint must match the authenticated user's user ID and the user must be a member of the account. The `signatureIdOrName` parameter accepts signature ID or signature name. DocuSign recommends you use signature ID (`signatureId`), since some names contain characters that don't properly URL encode. If you use the user name, it is likely that the name includes spaces and you might need to URL encode the name before using it in the endpoint. For example: \"Bob Smith\" to \"Bob%20Smith\" Older envelopes might only have chromed images. If getting the non-chromed image fails, try getting the chromed image. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param recipient_id The ID of the recipient being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :include_chrome When set to **true**, indicates the chromed version of the signature image should be retrieved. # @return [File] describe 'get_recipient_signature_image test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_template_recipient_document_visibility # Returns document visibility for the recipients # # @param account_id The external account number (int) or account ID Guid. # @param recipient_id The ID of the recipient being accessed. # @param template_id The ID of the template being accessed. # @param [Hash] opts the optional parameters # @return [DocumentVisibilityList] describe 'get_template_recipient_document_visibility test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for list_audit_events # Gets the envelope audit events for an envelope. # Gets the envelope audit events for the specified envelope. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @return [EnvelopeAuditEventResponse] describe 'list_audit_events test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for list_custom_fields # Gets the custom field information for the specified envelope. # Retrieves the custom field information for the specified envelope. You can use these fields in the envelopes for your account to record information about the envelope, help search for envelopes, and track information. The envelope custom fields are shown in the Envelope Settings section when a user is creating an envelope in the DocuSign member console. The envelope custom fields are not seen by the envelope recipients. There are two types of envelope custom fields, text, and list. A text custom field lets the sender enter the value for the field. With a list custom field, the sender selects the value of the field from a pre-made list. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @return [CustomFieldsEnvelope] describe 'list_custom_fields test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for list_document_fields # Gets the custom document fields from an existing envelope document. # Retrieves the custom document field information from an existing envelope document. # @param account_id The external account number (int) or account ID Guid. # @param document_id The ID of the document being accessed. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @return [DocumentFieldsInformation] describe 'list_document_fields test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for list_documents # Gets a list of envelope documents. # Retrieves a list of documents associated with the specified envelope. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :include_metadata # @return [EnvelopeDocumentsResult] describe 'list_documents test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for list_recipients # Gets the status of recipients for an envelope. # Retrieves the status of all recipients in a single envelope and identifies the current recipient in the routing list. The `currentRoutingOrder` property of the response contains the `routingOrder` value of the current recipient indicating that the envelope has been sent to the recipient, but the recipient has not completed their actions. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :include_anchor_tab_locations When set to **true** and `include_tabs` is set to **true**, all tabs with anchor tab properties are included in the response. # @option opts [String] :include_extended When set to **true**, the extended properties are included in the response. # @option opts [String] :include_metadata # @option opts [String] :include_tabs When set to **true**, the tab information associated with the recipient is included in the response. # @return [Recipients] describe 'list_recipients test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for list_status # Gets the envelope status for the specified envelopes. # Retrieves the envelope status for the specified envelopes. # @param account_id The external account number (int) or account ID Guid. # @param [Hash] opts the optional parameters # @option opts [String] :email # @option opts [String] :from_date # @option opts [String] :start_position # @option opts [String] :to_date # @option opts [EnvelopeIdsRequest] :envelope_ids_request # @return [EnvelopesInformation] describe 'list_status test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for list_status_changes # Gets status changes for one or more envelopes. # Retrieves envelope status changes for all envelopes. You can modify the information returned by adding query strings to limit the request to check between certain dates and times, or for certain envelopes, or for certain status codes. It is recommended that you use one or more of the query strings in order to limit the size of the response. ### Important: Unless you are requesting the status for specific envelopes (using the `envelopeIds` or `transactionIds` properties), you must add a set the `from_date` property in the request. Getting envelope status using `transactionIds` is useful for offline signing situations where it can be used determine if an envelope was created or not, for the cases where a network connection was lost, before the envelope status could be returned. ### Request Envelope Status Notes ### The REST API GET /envelopes call uses certain filters to find results. In some cases requests are check for \"any status change\" instead of the just the single status requested. In these cases, more envelopes might be returned by the request than otherwise would be. For example, for a request with the begin date is set to Jan 1st, an end date set to Jan 7th and the status qualifier (`from_to_status`) set to `Delivered` &mdash; the response set might contain envelopes that were created during that time period, but not delivered during the time period. To avoid unnecessary database queries, the DocuSign system checks requests to ensure that the added filters will not result in a zero-size response before acting on the request. The following table shows the valid envelope statuses (in the Valid Current Statuses column) for the status qualifiers in the request. If the status and status qualifiers in the API request do not contain any of the values shown in the valid current statuses column, then an empty list is returned. For example, a request with a status qualifier (from_to_status) of `Delivered` and a status of \"`Created`,`Sent`\", DocuSign will always return an empty list. This is because the request essentially translates to: find the envelopes that were delivered between the begin and end dates that have a current status of `Created` or `Sent`, and since an envelope that has been delivered can never have a status of `Created` or `Sent`, a zero-size response would be generated. In this case, DocuSign does not run the request, but just returns the empty list. Client applications should check that the statuses they are requesting make sense for a given status qualifier. # @param account_id The external account number (int) or account ID Guid. # @param [Hash] opts the optional parameters # @option opts [String] :ac_status Specifies the Authoritative Copy Status for the envelopes. The possible values are: Unknown, Original, Transferred, AuthoritativeCopy, AuthoritativeCopyExportPending, AuthoritativeCopyExported, DepositPending, Deposited, DepositedEO, or DepositFailed. # @option opts [String] :block # @option opts [String] :count # @option opts [String] :custom_field This specifies the envelope custom field name and value searched for in the envelope information. The value portion of the query can use partial strings by adding '%' (percent sign) around the custom field query value. Example 1: If you have an envelope custom field called \"Region\" and you want to search for all envelopes where the value is \"West\" you would use the query: `?custom_field=Region=West`. Example 2: To search for envelopes where the `ApplicationID` custom field has the value or partial value of \"DocuSign\" in field, the query would be: `?custom_field=ApplicationId=%DocuSign%` This would find envelopes where the custom field value is \"DocuSign for Salesforce\" or \"DocuSign envelope.\" # @option opts [String] :email # @option opts [String] :envelope_ids # @option opts [String] :exclude # @option opts [String] :folder_ids # @option opts [String] :folder_types # @option opts [String] :from_date The date/time setting that specifies the date/time when the request begins checking for status changes for envelopes in the account. This is required unless 'envelopeId's are used. # @option opts [String] :from_to_status This is the status type checked for in the `from_date`/`to_date` period. If `changed` is specified, then envelopes that changed status during the period are found. If for example, `created` is specified, then envelopes created during the period are found. Default is `changed`. Possible values are: Voided, Changed, Created, Deleted, Sent, Delivered, Signed, Completed, Declined, TimedOut and Processing. # @option opts [String] :include # @option opts [String] :intersecting_folder_ids # @option opts [String] :order # @option opts [String] :order_by # @option opts [String] :powerformids # @option opts [String] :search_text # @option opts [String] :start_position # @option opts [String] :status The list of current statuses to include in the response. By default, all envelopes found are returned. If values are specified, then of the envelopes found, only those with the current status specified are returned in the results. Possible values are: Voided, Created, Deleted, Sent, Delivered, Signed, Completed, Declined, TimedOut and Processing. # @option opts [String] :to_date Optional date/time setting that specifies the date/time when the request stops for status changes for envelopes in the account. If no entry, the system uses the time of the call as the `to_date`. # @option opts [String] :transaction_ids If included in the query string, this is a comma separated list of envelope `transactionId`s. If included in the `request_body`, this is a list of envelope `transactionId`s. ###### Note: `transactionId`s are only valid in the DocuSign system for seven days. # @option opts [String] :user_filter # @option opts [String] :user_id # @option opts [String] :user_name # @return [EnvelopesInformation] describe 'list_status_changes test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for list_tabs # Gets the tabs information for a signer or sign-in-person recipient in an envelope. # Retrieves information about the tabs associated with a recipient in a draft envelope. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param recipient_id The ID of the recipient being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :include_anchor_tab_locations When set to **true**, all tabs with anchor tab properties are included in the response. # @option opts [String] :include_metadata # @return [Tabs] describe 'list_tabs test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for list_templates # Get List of Templates used in an Envelope # This returns a list of the server-side templates, their name and ID, used in an envelope. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :include The possible values are: matching_applied – This returns template matching information for the template. # @return [TemplateInformation] describe 'list_templates test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for list_templates_for_document # Gets the templates associated with a document in an existing envelope. # Retrieves the templates associated with a document in the specified envelope. # @param account_id The external account number (int) or account ID Guid. # @param document_id The ID of the document being accessed. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :include # @return [TemplateInformation] describe 'list_templates_for_document test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for put_attachment # Add an attachment to a DRAFT or IN-PROCESS envelope. # # @param account_id The external account number (int) or account ID Guid. # @param attachment_id # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [Attachment] :attachment # @return [EnvelopeAttachmentsResult] describe 'put_attachment test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for put_attachments # Add one or more attachments to a DRAFT or IN-PROCESS envelope. # # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [EnvelopeAttachmentsRequest] :envelope_attachments_request # @return [EnvelopeAttachmentsResult] describe 'put_attachments test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for rotate_document_page # Rotates page image from an envelope for display. # Rotates page image from an envelope for display. The page image can be rotated to the left or right. # @param account_id The external account number (int) or account ID Guid. # @param document_id The ID of the document being accessed. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param page_number The page number being accessed. # @param [Hash] opts the optional parameters # @option opts [PageRequest] :page_request # @return [nil] describe 'rotate_document_page test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update # Send Draft Envelope/Void Envelope/Move/Purge Envelope/Modify draft # The Put Envelopes endpoint provides the following functionality: * Sends the specified single draft envelope. Add {\"status\":\"sent\"} to the request body to send the envelope. * Voids the specified in-process envelope. Add {\"status\":\"voided\", \"voidedReason\":\"The reason for voiding the envelope\"} to the request body to void the envelope. * Replaces the current email subject and message for a draft envelope. Add {\"emailSubject\":\"subject\", \"emailBlurb\":\"message\"} to the request body to modify the subject and message. * Place the envelope documents and envelope metadata in a purge queue so that this information is removed from the DocuSign system. Add {\"purgeState\":\"purge type\"} to the request body. *Additional information on purging documents* The purge request can only be used for completed envelopes that are not marked as the authoritative copy. The requesting user must have permission to purge documents and must be the sender (the requesting user can act as the sender using Send On Behalf Of). ###### Note: If you have set the Document Retention policy on your account, envelope documents are automatically placed in the purge queue and the warning emails are sent at the end of the retention period. ###### Note: You can set the Document Retention policy in the Classic DocuSign Experience by specifying the number of days to retain documents. ###### Note: Setting a Document Retention policy is the same as setting a schedule for purging documents. When the purge request is initiated the envelope documents, or documents and envelope metadata, are placed in a purge queue for deletion in 14 days. A warning email notification is sent to the sender and recipients associated with the envelope, notifying them that the envelope documents will be deleted in 14 days and providing a link to the documents. A second email is sent 7 days later with the same message. At the end of the 14-day period, the envelope documents are deleted from the system. If `purgeState=\"documents_queued\"` is used in the request, then only the documents are deleted and any corresponding attachments and tabs remain in the DocuSign system. If `purgeState= \"documents_and_metadata_queued\"` is used in the request, then the documents, attachments, and tabs are deleted. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :advanced_update When set to **true**, allows the caller to update recipients, tabs, custom fields, notification, email settings and other envelope attributes. # @option opts [String] :resend_envelope When set to **true**, sends the specified envelope again. # @option opts [Envelope] :envelope # @return [EnvelopeUpdateSummary] describe 'update test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_chunked_upload # Integrity-Check and Commit a ChunkedUpload, readying it for use elsewhere. # # @param account_id The external account number (int) or account ID Guid. # @param chunked_upload_id # @param [Hash] opts the optional parameters # @option opts [String] :action # @return [ChunkedUploadResponse] describe 'update_chunked_upload test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_chunked_upload_part # Add a chunk, a chunk 'part', to an existing ChunkedUpload. # # @param account_id The external account number (int) or account ID Guid. # @param chunked_upload_id # @param chunked_upload_part_seq # @param [Hash] opts the optional parameters # @option opts [ChunkedUploadRequest] :chunked_upload_request # @return [ChunkedUploadResponse] describe 'update_chunked_upload_part test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_custom_fields # Updates envelope custom fields in an envelope. # Updates the envelope custom fields in draft and in-process envelopes. Each custom field used in an envelope must have a unique name. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [CustomFields] :custom_fields # @return [CustomFields] describe 'update_custom_fields test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_document # Adds a document to an existing draft envelope. # Adds a document to an existing draft envelope. # @param account_id The external account number (int) or account ID Guid. # @param document_id The ID of the document being accessed. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :apply_document_fields # @return [nil] describe 'update_document test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_document_fields # Updates existing custom document fields in an existing envelope document. # Updates existing custom document fields in an existing envelope document. # @param account_id The external account number (int) or account ID Guid. # @param document_id The ID of the document being accessed. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [DocumentFieldsInformation] :document_fields_information # @return [DocumentFieldsInformation] describe 'update_document_fields test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_documents # Adds one or more documents to an existing envelope document. # Adds one or more documents to an existing envelope document. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :apply_document_fields When true, Document fields can be added or modified while adding or modifying envelope documents. # @option opts [EnvelopeDefinition] :envelope_definition # @return [EnvelopeDocumentsResult] describe 'update_documents test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_email_settings # Updates the email setting overrides for an envelope. # Updates the existing email override settings for the specified envelope. Note that modifying email settings will only affect email communications that occur after the modification was made. This can also be used to delete an individual email override setting by using an empty string for the value to be deleted. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [EmailSettings] :email_settings # @return [EmailSettings] describe 'update_email_settings test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_lock # Updates an envelope lock. # Updates the lock duration time or update the `lockedByApp` property information for the specified envelope. The user and integrator key must match the user specified by the `lockByUser` property and integrator key information and the `X-DocuSign-Edit` header must be included or an error will be generated. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [LockRequest] :lock_request # @return [LockInformation] describe 'update_lock test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_notification_settings # Sets envelope notification (Reminders/Expirations) structure for an existing envelope. # # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [EnvelopeNotificationRequest] :envelope_notification_request # @return [Notification] describe 'update_notification_settings test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_recipient_document_visibility # Updates document visibility for the recipients # # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param recipient_id The ID of the recipient being accessed. # @param [Hash] opts the optional parameters # @option opts [DocumentVisibilityList] :document_visibility_list # @return [DocumentVisibilityList] describe 'update_recipient_document_visibility test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_recipient_initials_image # Sets the initials image for an accountless signer. # Updates the initials image for a signer that does not have a DocuSign account. The supported image formats for this file are: gif, png, jpeg, and bmp. The file size must be less than 200K. For the Authentication/Authorization for this call, the credentials must match the sender of the envelope, the recipient must be an accountless signer or in person signer. The account must have the `CanSendEnvelope` property set to **true** and the `ExpressSendOnly` property in `SendingUser` structure must be set to **false**. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param recipient_id The ID of the recipient being accessed. # @param [Hash] opts the optional parameters # @return [nil] describe 'update_recipient_initials_image test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_recipient_signature_image # Sets the signature image for an accountless signer. # Updates the signature image for an accountless signer. The supported image formats for this file are: gif, png, jpeg, and bmp. The file size must be less than 200K. For the Authentication/Authorization for this call, the credentials must match the sender of the envelope, the recipient must be an accountless signer or in person signer. The account must have the `CanSendEnvelope` property set to **true** and the `ExpressSendOnly` property in `SendingUser` structure must be set to **false**. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param recipient_id The ID of the recipient being accessed. # @param [Hash] opts the optional parameters # @return [nil] describe 'update_recipient_signature_image test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_recipients # Updates recipients in a draft envelope or corrects recipient information for an in process envelope. # Updates recipients in a draft envelope or corrects recipient information for an in process envelope. For draft envelopes, you can edit the following properties: `email`, `userName`, `routingOrder`, `faxNumber`, `deliveryMethod`, `accessCode`, and `requireIdLookup`. Once an envelope has been sent, you can only edit: `email`, `userName`, `signerName`, `routingOrder`, `faxNumber`, and `deliveryMethod`. You can also select to resend an envelope by using the `resend_envelope` option. If you send information for a recipient that does not already exist in a draft envelope, the recipient is added to the envelope (similar to the POST). # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [String] :resend_envelope When set to **true**, resends the envelope if the new recipient's routing order is before or the same as the envelope’s next recipient. # @option opts [Recipients] :recipients # @return [RecipientsUpdateSummary] describe 'update_recipients test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_recipients_document_visibility # Updates document visibility for the recipients # # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param [Hash] opts the optional parameters # @option opts [DocumentVisibilityList] :document_visibility_list # @return [DocumentVisibilityList] describe 'update_recipients_document_visibility test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_tabs # Updates the tabs for a recipient. # Updates one or more tabs for a recipient in a draft envelope. # @param account_id The external account number (int) or account ID Guid. # @param envelope_id The envelopeId Guid of the envelope being accessed. # @param recipient_id The ID of the recipient being accessed. # @param [Hash] opts the optional parameters # @option opts [Tabs] :tabs # @return [Tabs] describe 'update_tabs test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_template_recipient_document_visibility # Updates document visibility for the recipients # # @param account_id The external account number (int) or account ID Guid. # @param recipient_id The ID of the recipient being accessed. # @param template_id The ID of the template being accessed. # @param [Hash] opts the optional parameters # @option opts [TemplateDocumentVisibilityList] :template_document_visibility_list # @return [TemplateDocumentVisibilityList] describe 'update_template_recipient_document_visibility test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_template_recipients_document_visibility # Updates document visibility for the recipients # # @param account_id The external account number (int) or account ID Guid. # @param template_id The ID of the template being accessed. # @param [Hash] opts the optional parameters # @option opts [TemplateDocumentVisibilityList] :template_document_visibility_list # @return [TemplateDocumentVisibilityList] describe 'update_template_recipients_document_visibility test' do it "should work" do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end end