dropbox-sign 1.10.0 → 1.11.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 658cd13873defe21b2bb1abdb854d39494a769d4b67e1debb06ccd34bcb56d84
-  data.tar.gz: 91f087be8a111a7176fcb8eb19eb8ae11aef29e4bf501e038f956f08b9a000bb
+  metadata.gz: 85c8c09a1ecd4a5246f078f22ee2f3c9ce4ee49ef9c515abb27d65afb79596bd
+  data.tar.gz: '09743f339f596a29c7d85ed4238f11d1e387815e4ec3d8d7c9de8e863fba3d9f'
 SHA512:
-  metadata.gz: a50c35972931981401e102c4cf615569a83654e75a893474275489d6cc7e354f9f3dcdb7e0c794ffbab82b08dbdb04eb963ce95fcd9584bf66fd965c5e61f303
-  data.tar.gz: 327b4f666afb49f4869e7922cdf3baae55b8499be31a8320b64a97b7deb30eccf3227ff1bd63ced7b2930fd0967c0789622e0f5d617972ba40e25c4af5bceff5
+  metadata.gz: a61abfe634182db829cba1c2367b52baa0dada0bd48c1e437e6b5229ce8db99bf419670966e5b31c6c91c8987e96f8ea10358bcde7d58888b53df93c3867935e
+  data.tar.gz: 4124389a9610fb384a75880ed40e4b8cbde7c7a1a430b9cf6ddef5ceca0eb2b0922f82824814348d4cdcb23b3ae03ec5064b22c3c7e23bcc7ca39ecf5af77da6

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    dropbox-sign (1.10.0)
+    dropbox-sign (1.11.0)
       typhoeus (~> 1.0, >= 1.0.1)
 
 GEM
@@ -11,17 +11,19 @@ GEM
     byebug (11.1.3)
     coderay (1.1.3)
     diff-lcs (1.5.1)
-    ethon (0.16.0)
+    ethon (0.18.0)
       ffi (>= 1.15.0)
-    ffi (1.17.2-aarch64-linux-gnu)
-    ffi (1.17.2-arm64-darwin)
-    ffi (1.17.2-x86_64-darwin)
-    ffi (1.17.2-x86_64-linux-gnu)
+      logger
+    ffi (1.17.4-aarch64-linux-gnu)
+    ffi (1.17.4-arm64-darwin)
+    ffi (1.17.4-x86_64-darwin)
+    ffi (1.17.4-x86_64-linux-gnu)
     json (2.7.2)
     json_spec (1.1.5)
       multi_json (~> 1.0)
       rspec (>= 2.0, < 4.0)
     language_server-protocol (3.17.0.3)
+    logger (1.7.0)
     method_source (1.1.0)
     multi_json (1.15.0)
     parallel (1.26.3)
@@ -64,8 +66,8 @@ GEM
     rubocop-ast (1.32.3)
       parser (>= 3.3.1.0)
     ruby-progressbar (1.13.0)
-    typhoeus (1.4.1)
-      ethon (>= 0.9.0)
+    typhoeus (1.6.0)
+      ethon (>= 0.18.0)
     unicode-display_width (2.5.0)
 
 PLATFORMS

data/README.md

@@ -25,7 +25,7 @@ directory that corresponds to the file you want updated.
 This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
 
 - API version: 3.0.0
-- Package version: 1.10.0
+- Package version: 1.11.0
 - Generator version: 7.12.0
 - Build package: org.openapitools.codegen.languages.RubyClientCodegen
 
@@ -47,15 +47,15 @@ gem build dropbox-sign.gemspec
 Then install the gem locally:
 
 ```shell
-gem install ./dropbox-sign-1.10.0.gem
+gem install ./dropbox-sign-1.11.0.gem
 ```
 
-(for development, run `gem install --dev ./dropbox-sign-1.10.0.gem` to install the development dependencies)
+(for development, run `gem install --dev ./dropbox-sign-1.11.0.gem` to install the development dependencies)
 
 
 Finally add this to the Gemfile:
 
-    gem 'dropbox-sign', '~> 1.10.0'
+    gem 'dropbox-sign', '~> 1.11.0'
 
 ### Install from Git
 
@@ -189,6 +189,7 @@ All URIs are relative to *https://api.hellosign.com/v3*
  - [Dropbox::Sign::AccountGetResponse](docs/AccountGetResponse.md)
  - [Dropbox::Sign::AccountResponse](docs/AccountResponse.md)
  - [Dropbox::Sign::AccountResponseQuotas](docs/AccountResponseQuotas.md)
+ - [Dropbox::Sign::AccountResponseSettings](docs/AccountResponseSettings.md)
  - [Dropbox::Sign::AccountResponseUsage](docs/AccountResponseUsage.md)
  - [Dropbox::Sign::AccountUpdateRequest](docs/AccountUpdateRequest.md)
  - [Dropbox::Sign::AccountVerifyRequest](docs/AccountVerifyRequest.md)
@@ -332,7 +333,6 @@ All URIs are relative to *https://api.hellosign.com/v3*
  - [Dropbox::Sign::TemplateCreateRequest](docs/TemplateCreateRequest.md)
  - [Dropbox::Sign::TemplateCreateResponse](docs/TemplateCreateResponse.md)
  - [Dropbox::Sign::TemplateCreateResponseTemplate](docs/TemplateCreateResponseTemplate.md)
- - [Dropbox::Sign::TemplateEditResponse](docs/TemplateEditResponse.md)
  - [Dropbox::Sign::TemplateGetResponse](docs/TemplateGetResponse.md)
  - [Dropbox::Sign::TemplateListResponse](docs/TemplateListResponse.md)
  - [Dropbox::Sign::TemplateRemoveUserRequest](docs/TemplateRemoveUserRequest.md)

data/VERSION

@@ -1 +1 @@
-1.10.0
+1.11.0

data/docs/AccountResponse.md

@@ -17,4 +17,5 @@
 | `team_id` | ```String``` |  The id of the team account belongs to.  |  |
 | `locale` | ```String``` |  The locale used in this Account. Check out the list of [supported locales](/api/reference/constants/#supported-locales) to learn more about the possible values.  |  |
 | `usage` | [```AccountResponseUsage```](AccountResponseUsage.md) |    |  |
+| `settings` | [```AccountResponseSettings```](AccountResponseSettings.md) |    |  |
 

data/docs/AccountResponseSettings.md

@@ -0,0 +1,12 @@
+# Dropbox::Sign::AccountResponseSettings
+
+Subset of configured settings
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| `signer_access_codes` | ```Boolean``` |  Returns `true` if _Custom access codes_ is enabled in Admin Console. [Read more](https://developers.hellosign.com/docs/sms-tools/walkthrough).  |  |
+| `sms_delivery` | ```Boolean``` |  Returns `true` if _Text message_ is enabled in Admin Console. [Read more](https://developers.hellosign.com/docs/sms-tools/walkthrough).  |  |
+| `sms_authentication` | ```Boolean``` |  Returns `true` if _Signer authentication_ is enabled in Admin Console. [Read more](https://developers.hellosign.com/docs/sms-tools/walkthrough).  |  |
+

data/docs/SignatureRequestApi.md

@@ -390,6 +390,7 @@ signing_options.draw = true
 signing_options.phone = false
 signing_options.type = true
 signing_options.upload = true
+signing_options.force_advanced_signature_details = false
 
 signers_1 = Dropbox::Sign::SubSignatureRequestSigner.new
 signers_1.name = "Jack"
@@ -497,6 +498,7 @@ signing_options.draw = true
 signing_options.phone = false
 signing_options.type = true
 signing_options.upload = true
+signing_options.force_advanced_signature_details = false
 
 signers_1 = Dropbox::Sign::SubSignatureRequestTemplateSigner.new
 signers_1.role = "Client"
@@ -1609,6 +1611,7 @@ signing_options.draw = true
 signing_options.phone = false
 signing_options.type = true
 signing_options.upload = true
+signing_options.force_advanced_signature_details = false
 
 signers_1 = Dropbox::Sign::SubSignatureRequestSigner.new
 signers_1.name = "Jack"
@@ -1723,6 +1726,7 @@ signing_options.draw = true
 signing_options.phone = false
 signing_options.type = true
 signing_options.upload = true
+signing_options.force_advanced_signature_details = false
 
 signers_1 = Dropbox::Sign::SubSignatureRequestTemplateSigner.new
 signers_1.role = "Client"

data/docs/SignatureRequestEditRequest.md

@@ -21,7 +21,7 @@
 | `form_field_rules` | [```Array<SubFormFieldRule>```](SubFormFieldRule.md) |  Conditional Logic rules for fields defined in `form_fields_per_document`.  |  |
 | `form_fields_per_document` | [```Array<SubFormFieldsPerDocumentBase>```](SubFormFieldsPerDocumentBase.md) |  The fields that should appear on the document, expressed as an array of objects. (For more details you can read about it here: [Using Form Fields per Document](/docs/openapi/form-fields-per-document).)<br><br>**NOTE:** Fields like **text**, **dropdown**, **checkbox**, **radio**, and **hyperlink** have additional required and optional parameters. Check out the list of [additional parameters](/api/reference/constants/#form-fields-per-document) for these field types.<br><br>* Text Field use `SubFormFieldsPerDocumentText`<br>* Dropdown Field use `SubFormFieldsPerDocumentDropdown`<br>* Hyperlink Field use `SubFormFieldsPerDocumentHyperlink`<br>* Checkbox Field use `SubFormFieldsPerDocumentCheckbox`<br>* Radio Field use `SubFormFieldsPerDocumentRadio`<br>* Signature Field use `SubFormFieldsPerDocumentSignature`<br>* Date Signed Field use `SubFormFieldsPerDocumentDateSigned`<br>* Initials Field use `SubFormFieldsPerDocumentInitials`<br>* Text Merge Field use `SubFormFieldsPerDocumentTextMerge`<br>* Checkbox Merge Field use `SubFormFieldsPerDocumentCheckboxMerge`  |  |
 | `hide_text_tags` | ```Boolean``` |  Enables automatic Text Tag removal when set to true.<br><br>**NOTE:** Removing text tags this way can cause unwanted clipping. We recommend leaving this setting on `false` and instead hiding your text tags using white text or a similar approach. See the [Text Tags Walkthrough](https://app.hellosign.com/api/textTagsWalkthrough#TextTagIntro) for more information.  |  [default to false] |
-| `is_eid` | ```Boolean``` |  Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.&lt;br&gt;<br>**NOTE:** eID is only available on the Premium API plan. Cannot be used in `test_mode`. Only works on requests with one signer.  |  [default to false] |
+| `is_eid` | ```Boolean``` |  Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.&lt;br&gt;<br>**NOTE:** You need the eID add-on to use this feature. Please [contact sales](https://sign.dropbox.com/form/contact-sales) for more information. Cannot be used in `test_mode`. Only works on requests with one signer.  |  [default to false] |
 | `message` | ```String``` |  The custom message in the email that will be sent to the signers.  |  |
 | `metadata` | ```Hash<String, Object>``` |  Key-value data that should be attached to the signature request. This metadata is included in all API responses and events involving the signature request. For example, use the metadata field to store a signer&#39;s order number for look up when receiving events for the signature request.<br><br>Each request can include up to 10 metadata keys (or 50 nested metadata keys), with key names up to 40 characters long and values up to 1000 characters long.  |  |
 | `signing_options` | [```SubSigningOptions```](SubSigningOptions.md) |    |  |

data/docs/SignatureRequestEditWithTemplateRequest.md

@@ -14,7 +14,7 @@
 | `custom_fields` | [```Array<SubCustomField>```](SubCustomField.md) |  An array defining values and options for custom fields. Required when a custom field exists in the Template.  |  |
 | `files` | ```Array<File>``` |  Use `files[]` to indicate the uploaded file(s) to send for signature.<br><br>This endpoint requires either **files** or **file_urls[]**, but not both.  |  |
 | `file_urls` | ```Array<String>``` |  Use `file_urls[]` to have Dropbox Sign download the file(s) to send for signature.<br><br>This endpoint requires either **files** or **file_urls[]**, but not both.  |  |
-| `is_eid` | ```Boolean``` |  Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.&lt;br&gt;<br>**NOTE:** eID is only available on the Premium API plan. Cannot be used in `test_mode`. Only works on requests with one signer.  |  [default to false] |
+| `is_eid` | ```Boolean``` |  Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.&lt;br&gt;<br>**NOTE:** You need the eID add-on to use this feature. Please [contact sales](https://sign.dropbox.com/form/contact-sales) for more information. Cannot be used in `test_mode`. Only works on requests with one signer.  |  [default to false] |
 | `message` | ```String``` |  The custom message in the email that will be sent to the signers.  |  |
 | `metadata` | ```Hash<String, Object>``` |  Key-value data that should be attached to the signature request. This metadata is included in all API responses and events involving the signature request. For example, use the metadata field to store a signer&#39;s order number for look up when receiving events for the signature request.<br><br>Each request can include up to 10 metadata keys (or 50 nested metadata keys), with key names up to 40 characters long and values up to 1000 characters long.  |  |
 | `signing_options` | [```SubSigningOptions```](SubSigningOptions.md) |    |  |

data/docs/SignatureRequestSendRequest.md

@@ -22,7 +22,7 @@
 | `form_fields_per_document` | [```Array<SubFormFieldsPerDocumentBase>```](SubFormFieldsPerDocumentBase.md) |  The fields that should appear on the document, expressed as an array of objects. (For more details you can read about it here: [Using Form Fields per Document](/docs/openapi/form-fields-per-document).)<br><br>**NOTE:** Fields like **text**, **dropdown**, **checkbox**, **radio**, and **hyperlink** have additional required and optional parameters. Check out the list of [additional parameters](/api/reference/constants/#form-fields-per-document) for these field types.<br><br>* Text Field use `SubFormFieldsPerDocumentText`<br>* Dropdown Field use `SubFormFieldsPerDocumentDropdown`<br>* Hyperlink Field use `SubFormFieldsPerDocumentHyperlink`<br>* Checkbox Field use `SubFormFieldsPerDocumentCheckbox`<br>* Radio Field use `SubFormFieldsPerDocumentRadio`<br>* Signature Field use `SubFormFieldsPerDocumentSignature`<br>* Date Signed Field use `SubFormFieldsPerDocumentDateSigned`<br>* Initials Field use `SubFormFieldsPerDocumentInitials`<br>* Text Merge Field use `SubFormFieldsPerDocumentTextMerge`<br>* Checkbox Merge Field use `SubFormFieldsPerDocumentCheckboxMerge`  |  |
 | `hide_text_tags` | ```Boolean``` |  Enables automatic Text Tag removal when set to true.<br><br>**NOTE:** Removing text tags this way can cause unwanted clipping. We recommend leaving this setting on `false` and instead hiding your text tags using white text or a similar approach. See the [Text Tags Walkthrough](https://app.hellosign.com/api/textTagsWalkthrough#TextTagIntro) for more information.  |  [default to false] |
 | `is_qualified_signature` | ```Boolean``` |  Send with a value of `true` if you wish to enable [Qualified Electronic Signatures](https://www.hellosign.com/features/qualified-electronic-signatures) (QES), which requires a face-to-face call to verify the signer&#39;s identity.&lt;br&gt;<br>**NOTE:** QES is only available on the Premium API plan as an add-on purchase. Cannot be used in `test_mode`. Only works on requests with one signer.  |  [default to false] |
-| `is_eid` | ```Boolean``` |  Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.&lt;br&gt;<br>**NOTE:** eID is only available on the Premium API plan. Cannot be used in `test_mode`. Only works on requests with one signer.  |  [default to false] |
+| `is_eid` | ```Boolean``` |  Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.&lt;br&gt;<br>**NOTE:** You need the eID add-on to use this feature. Please [contact sales](https://sign.dropbox.com/form/contact-sales) for more information. Cannot be used in `test_mode`. Only works on requests with one signer.  |  [default to false] |
 | `message` | ```String``` |  The custom message in the email that will be sent to the signers.  |  |
 | `metadata` | ```Hash<String, Object>``` |  Key-value data that should be attached to the signature request. This metadata is included in all API responses and events involving the signature request. For example, use the metadata field to store a signer&#39;s order number for look up when receiving events for the signature request.<br><br>Each request can include up to 10 metadata keys (or 50 nested metadata keys), with key names up to 40 characters long and values up to 1000 characters long.  |  |
 | `signing_options` | [```SubSigningOptions```](SubSigningOptions.md) |    |  |

data/docs/SignatureRequestSendWithTemplateRequest.md

@@ -15,7 +15,7 @@
 | `files` | ```Array<File>``` |  Use `files[]` to indicate the uploaded file(s) to send for signature.<br><br>This endpoint requires either **files** or **file_urls[]**, but not both.  |  |
 | `file_urls` | ```Array<String>``` |  Use `file_urls[]` to have Dropbox Sign download the file(s) to send for signature.<br><br>This endpoint requires either **files** or **file_urls[]**, but not both.  |  |
 | `is_qualified_signature` | ```Boolean``` |  Send with a value of `true` if you wish to enable [Qualified Electronic Signatures](https://www.hellosign.com/features/qualified-electronic-signatures) (QES), which requires a face-to-face call to verify the signer&#39;s identity.&lt;br&gt;<br>**NOTE:** QES is only available on the Premium API plan as an add-on purchase. Cannot be used in `test_mode`. Only works on requests with one signer.  |  [default to false] |
-| `is_eid` | ```Boolean``` |  Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.&lt;br&gt;<br>**NOTE:** eID is only available on the Premium API plan. Cannot be used in `test_mode`. Only works on requests with one signer.  |  [default to false] |
+| `is_eid` | ```Boolean``` |  Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.&lt;br&gt;<br>**NOTE:** You need the eID add-on to use this feature. Please [contact sales](https://sign.dropbox.com/form/contact-sales) for more information. Cannot be used in `test_mode`. Only works on requests with one signer.  |  [default to false] |
 | `message` | ```String``` |  The custom message in the email that will be sent to the signers.  |  |
 | `metadata` | ```Hash<String, Object>``` |  Key-value data that should be attached to the signature request. This metadata is included in all API responses and events involving the signature request. For example, use the metadata field to store a signer&#39;s order number for look up when receiving events for the signature request.<br><br>Each request can include up to 10 metadata keys (or 50 nested metadata keys), with key names up to 40 characters long and values up to 1000 characters long.  |  |
 | `signing_options` | [```SubSigningOptions```](SubSigningOptions.md) |    |  |

data/docs/SubSigningOptions.md

@@ -1,9 +1,11 @@
 # Dropbox::Sign::SubSigningOptions
 
-This allows the requester to specify the types allowed for creating a signature.
+This allows the requester to specify the types allowed for creating a signature and specify another signing options.
 
 **NOTE:** If `signing_options` are not defined in the request, the allowed types will default to those specified in the account settings.
 
+**NOTE:** If `force_advanced_signature_details` is set, allowed types has to be defined too.
+
 ## Properties
 
 | Name | Type | Description | Notes |
@@ -13,4 +15,5 @@ This allows the requester to specify the types allowed for creating a signature.
 | `phone` | ```Boolean``` |  Allows using a smartphone to email the signature  |  [default to false] |
 | `type` | ```Boolean``` |  Allows typing the signature  |  [default to false] |
 | `upload` | ```Boolean``` |  Allows uploading the signature  |  [default to false] |
+| `force_advanced_signature_details` | ```Boolean``` |  Turning on advanced signature details for the signature request  |  [default to false] |
 

data/docs/TemplateApi.md

@@ -97,7 +97,7 @@ end
 
 Create Template
 
-Creates a template that can then be used.
+Creates a template that can be used in future signature requests.  If `client_id` is provided, the template will be created as an embedded template. Embedded templates can be used for embedded signature requests and can be edited later by generating a new `edit_url` with [/embedded/edit_url/{template_id}](/api/reference/operation/embeddedEditUrl/).  Template creation may complete asynchronously after the initial request is accepted. It is recommended that a callback be implemented to listen for the callback event. A `template_created` event indicates the template is ready to use, while a `template_error` event indicates there was a problem while creating the template. If a callback handler has been configured and the event has not been received within 60 minutes of making the call, check the status of the request in the API dashboard and retry the request if necessary.
 
 ### Examples
 

data/examples/SignatureRequestCreateEmbeddedExample.rb

@@ -12,6 +12,7 @@ signing_options.draw = true
 signing_options.phone = false
 signing_options.type = true
 signing_options.upload = true
+signing_options.force_advanced_signature_details = false
 
 signers_1 = Dropbox::Sign::SubSignatureRequestSigner.new
 signers_1.name = "Jack"

data/examples/SignatureRequestCreateEmbeddedWithTemplateExample.rb

@@ -12,6 +12,7 @@ signing_options.draw = true
 signing_options.phone = false
 signing_options.type = true
 signing_options.upload = true
+signing_options.force_advanced_signature_details = false
 
 signers_1 = Dropbox::Sign::SubSignatureRequestTemplateSigner.new
 signers_1.role = "Client"

data/examples/SignatureRequestSendExample.rb

@@ -15,6 +15,7 @@ signing_options.draw = true
 signing_options.phone = false
 signing_options.type = true
 signing_options.upload = true
+signing_options.force_advanced_signature_details = false
 
 signers_1 = Dropbox::Sign::SubSignatureRequestSigner.new
 signers_1.name = "Jack"

data/examples/SignatureRequestSendWithTemplateExample.rb

@@ -12,6 +12,7 @@ signing_options.draw = true
 signing_options.phone = false
 signing_options.type = true
 signing_options.upload = true
+signing_options.force_advanced_signature_details = false
 
 signers_1 = Dropbox::Sign::SubSignatureRequestTemplateSigner.new
 signers_1.role = "Client"

data/lib/dropbox-sign/api/template_api.rb

@@ -138,7 +138,7 @@ module Dropbox::Sign
     end
 
     # Create Template
-    # Creates a template that can then be used.
+    # Creates a template that can be used in future signature requests.  If `client_id` is provided, the template will be created as an embedded template. Embedded templates can be used for embedded signature requests and can be edited later by generating a new `edit_url` with [/embedded/edit_url/{template_id}](/api/reference/operation/embeddedEditUrl/).  Template creation may complete asynchronously after the initial request is accepted. It is recommended that a callback be implemented to listen for the callback event. A `template_created` event indicates the template is ready to use, while a `template_error` event indicates there was a problem while creating the template. If a callback handler has been configured and the event has not been received within 60 minutes of making the call, check the status of the request in the API dashboard and retry the request if necessary.
     # @param template_create_request [TemplateCreateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [TemplateCreateResponse]
@@ -148,7 +148,7 @@ module Dropbox::Sign
     end
 
     # Create Template
-    # Creates a template that can then be used.
+    # Creates a template that can be used in future signature requests.  If `client_id` is provided, the template will be created as an embedded template. Embedded templates can be used for embedded signature requests and can be edited later by generating a new `edit_url` with [/embedded/edit_url/{template_id}](/api/reference/operation/embeddedEditUrl/).  Template creation may complete asynchronously after the initial request is accepted. It is recommended that a callback be implemented to listen for the callback event. A `template_created` event indicates the template is ready to use, while a `template_error` event indicates there was a problem while creating the template. If a callback handler has been configured and the event has not been received within 60 minutes of making the call, check the status of the request in the API dashboard and retry the request if necessary.
     # @param template_create_request [TemplateCreateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(TemplateCreateResponse, Integer, Hash)>] TemplateCreateResponse data, response status code and response headers

data/lib/dropbox-sign/api_client.rb

@@ -132,6 +132,22 @@ module Dropbox::Sign
         end
       end
 
+      # Workaround for the Typhoeus/libcurl multipart PUT bug.
+      # libcurl only builds a multipart body via CURLOPT_HTTPPOST/CURLOPT_MIMEPOST,
+      # which is engaged for POST requests. For PUT it falls back to CURLOPT_UPLOAD
+      # and silently drops form fields, so the request is sent without a
+      # `Content-Type: multipart/form-data; boundary=...` header or body.
+      # We send the request as POST so the multipart body is encoded correctly,
+      # then use CURLOPT_CUSTOMREQUEST (exposed by Ethon as :customrequest) to
+      # restore PUT as the on-the-wire HTTP verb.
+      # See: https://github.com/typhoeus/typhoeus/issues/389
+      content_type_header = header_params['Content-Type'] || header_params['content-type']
+      if http_method == :put && content_type_header.is_a?(String) &&
+         content_type_header.start_with?('multipart/form-data')
+        req_opts[:method] = :post
+        req_opts[:customrequest] = 'PUT'
+      end
+
       Typhoeus::Request.new(url, req_opts)
     end
 

data/lib/dropbox-sign/models/account_response.rb

@@ -60,6 +60,9 @@ module Dropbox::Sign
     # @return [AccountResponseUsage]
     attr_accessor :usage
 
+    # @return [AccountResponseSettings]
+    attr_accessor :settings
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
@@ -73,7 +76,8 @@ module Dropbox::Sign
         :'role_code' => :'role_code',
         :'team_id' => :'team_id',
         :'locale' => :'locale',
-        :'usage' => :'usage'
+        :'usage' => :'usage',
+        :'settings' => :'settings'
       }
     end
 
@@ -100,7 +104,8 @@ module Dropbox::Sign
         :'role_code' => :'String',
         :'team_id' => :'String',
         :'locale' => :'String',
-        :'usage' => :'AccountResponseUsage'
+        :'usage' => :'AccountResponseUsage',
+        :'settings' => :'AccountResponseSettings'
       }
     end
 
@@ -198,6 +203,10 @@ module Dropbox::Sign
       if attributes.key?(:'usage')
         self.usage = attributes[:'usage']
       end
+
+      if attributes.key?(:'settings')
+        self.settings = attributes[:'settings']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -228,7 +237,8 @@ module Dropbox::Sign
           role_code == o.role_code &&
           team_id == o.team_id &&
           locale == o.locale &&
-          usage == o.usage
+          usage == o.usage &&
+          settings == o.settings
     end
 
     # @see the `==` method
@@ -240,7 +250,7 @@ module Dropbox::Sign
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [account_id, email_address, is_locked, is_paid_hs, is_paid_hf, quotas, callback_url, role_code, team_id, locale, usage].hash
+      [account_id, email_address, is_locked, is_paid_hs, is_paid_hf, quotas, callback_url, role_code, team_id, locale, usage, settings].hash
     end
 
     # Builds the object from hash

data/lib/dropbox-sign/models/{template_edit_response.rb → account_response_settings.rb}

@@ -17,15 +17,26 @@ module Dropbox
 end
 
 module Dropbox::Sign
-  class TemplateEditResponse
-    # The id of the Template.
-    # @return [String]
-    attr_accessor :template_id
+  # Subset of configured settings
+  class AccountResponseSettings
+    # Returns `true` if _Custom access codes_ is enabled in Admin Console. [Read more](https://developers.hellosign.com/docs/sms-tools/walkthrough).
+    # @return [Boolean]
+    attr_accessor :signer_access_codes
+
+    # Returns `true` if _Text message_ is enabled in Admin Console. [Read more](https://developers.hellosign.com/docs/sms-tools/walkthrough).
+    # @return [Boolean]
+    attr_accessor :sms_delivery
+
+    # Returns `true` if _Signer authentication_ is enabled in Admin Console. [Read more](https://developers.hellosign.com/docs/sms-tools/walkthrough).
+    # @return [Boolean]
+    attr_accessor :sms_authentication
 
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
-        :'template_id' => :'template_id'
+        :'signer_access_codes' => :'signer_access_codes',
+        :'sms_delivery' => :'sms_delivery',
+        :'sms_authentication' => :'sms_authentication'
       }
     end
 
@@ -42,7 +53,9 @@ module Dropbox::Sign
     # Attribute type mapping.
     def self.openapi_types
       {
-        :'template_id' => :'String'
+        :'signer_access_codes' => :'Boolean',
+        :'sms_delivery' => :'Boolean',
+        :'sms_authentication' => :'Boolean'
       }
     end
 
@@ -69,32 +82,40 @@ module Dropbox::Sign
 
     # Attempt to instantiate and hydrate a new instance of this class
     # @param [Object] data Data to be converted
-    # @return [TemplateEditResponse]
+    # @return [AccountResponseSettings]
     def self.init(data)
       ApiClient.default.convert_to_type(
         data,
-        "TemplateEditResponse"
-      ) || TemplateEditResponse.new
+        "AccountResponseSettings"
+      ) || AccountResponseSettings.new
     end
 
     # Initializes the object
     # @param [Hash] attributes Model attributes in the form of hash
     def initialize(attributes = {})
       if (!attributes.is_a?(Hash))
-        fail ArgumentError, "The input argument (attributes) must be a hash in `Dropbox::Sign::TemplateEditResponse` initialize method"
+        fail ArgumentError, "The input argument (attributes) must be a hash in `Dropbox::Sign::AccountResponseSettings` initialize method"
       end
 
       # check to see if the attribute exists and convert string to symbol for hash key
       acceptable_attribute_map = self.class.acceptable_attribute_map
       attributes = attributes.each_with_object({}) { |(k, v), h|
         if (!self.class.merged_attributes.key?(k.to_sym))
-          fail ArgumentError, "`#{k}` is not a valid attribute in `Dropbox::Sign::TemplateEditResponse`. Please check the name to make sure it's valid. List of attributes: " + acceptable_attribute_map.keys.inspect
+          fail ArgumentError, "`#{k}` is not a valid attribute in `Dropbox::Sign::AccountResponseSettings`. Please check the name to make sure it's valid. List of attributes: " + acceptable_attribute_map.keys.inspect
         end
         h[k.to_sym] = v
       }
 
-      if attributes.key?(:'template_id')
-        self.template_id = attributes[:'template_id']
+      if attributes.key?(:'signer_access_codes')
+        self.signer_access_codes = attributes[:'signer_access_codes']
+      end
+
+      if attributes.key?(:'sms_delivery')
+        self.sms_delivery = attributes[:'sms_delivery']
+      end
+
+      if attributes.key?(:'sms_authentication')
+        self.sms_authentication = attributes[:'sms_authentication']
       end
     end
 
@@ -102,36 +123,23 @@ module Dropbox::Sign
     # @return Array for valid properties with the reasons
     def list_invalid_properties
       invalid_properties = Array.new
-      if @template_id.nil?
-        invalid_properties.push('invalid value for "template_id", template_id cannot be nil.')
-      end
-
       invalid_properties
     end
 
     # Check to see if the all the properties in the model are valid
     # @return true if the model is valid
     def valid?
-      return false if @template_id.nil?
       true
     end
 
-    # Custom attribute writer method with validation
-    # @param [Object] template_id Value to be assigned
-    def template_id=(template_id)
-      if template_id.nil?
-        fail ArgumentError, 'template_id cannot be nil'
-      end
-
-      @template_id = template_id
-    end
-
     # Checks equality by comparing each attribute.
     # @param [Object] Object to be compared
     def ==(o)
       return true if self.equal?(o)
       self.class == o.class &&
-          template_id == o.template_id
+          signer_access_codes == o.signer_access_codes &&
+          sms_delivery == o.sms_delivery &&
+          sms_authentication == o.sms_authentication
     end
 
     # @see the `==` method
@@ -143,7 +151,7 @@ module Dropbox::Sign
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [template_id].hash
+      [signer_access_codes, sms_delivery, sms_authentication].hash
     end
 
     # Builds the object from hash

data/lib/dropbox-sign/models/signature_request_edit_request.rb

@@ -77,7 +77,7 @@ module Dropbox::Sign
     # @return [Boolean]
     attr_accessor :hide_text_tags
 
-    # Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.<br> **NOTE:** eID is only available on the Premium API plan. Cannot be used in `test_mode`. Only works on requests with one signer.
+    # Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.<br> **NOTE:** You need the eID add-on to use this feature. Please [contact sales](https://sign.dropbox.com/form/contact-sales) for more information. Cannot be used in `test_mode`. Only works on requests with one signer.
     # @return [Boolean]
     attr_accessor :is_eid
 

data/lib/dropbox-sign/models/signature_request_edit_with_template_request.rb

@@ -51,7 +51,7 @@ module Dropbox::Sign
     # @return [Array<String>]
     attr_accessor :file_urls
 
-    # Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.<br> **NOTE:** eID is only available on the Premium API plan. Cannot be used in `test_mode`. Only works on requests with one signer.
+    # Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.<br> **NOTE:** You need the eID add-on to use this feature. Please [contact sales](https://sign.dropbox.com/form/contact-sales) for more information. Cannot be used in `test_mode`. Only works on requests with one signer.
     # @return [Boolean]
     attr_accessor :is_eid
 

data/lib/dropbox-sign/models/signature_request_send_request.rb

@@ -81,7 +81,7 @@ module Dropbox::Sign
     # @return [Boolean]
     attr_accessor :is_qualified_signature
 
-    # Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.<br> **NOTE:** eID is only available on the Premium API plan. Cannot be used in `test_mode`. Only works on requests with one signer.
+    # Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.<br> **NOTE:** You need the eID add-on to use this feature. Please [contact sales](https://sign.dropbox.com/form/contact-sales) for more information. Cannot be used in `test_mode`. Only works on requests with one signer.
     # @return [Boolean]
     attr_accessor :is_eid
 

data/lib/dropbox-sign/models/signature_request_send_with_template_request.rb

@@ -55,7 +55,7 @@ module Dropbox::Sign
     # @return [Boolean]
     attr_accessor :is_qualified_signature
 
-    # Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.<br> **NOTE:** eID is only available on the Premium API plan. Cannot be used in `test_mode`. Only works on requests with one signer.
+    # Send with a value of `true` if you wish to enable [electronic identification (eID)](https://www.hellosign.com/features/electronic-id), which requires the signer to verify their identity with an eID provider to sign a document.<br> **NOTE:** You need the eID add-on to use this feature. Please [contact sales](https://sign.dropbox.com/form/contact-sales) for more information. Cannot be used in `test_mode`. Only works on requests with one signer.
     # @return [Boolean]
     attr_accessor :is_eid