dropbox-sign 1.4.0 → 1.4.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 19e7be09ec4ca8eed92a4bfc2c49920e50ff01a1ea696e4bbdf8c1c9ac1918ea
-  data.tar.gz: 72c5f408ae6dda210cb045ba722f2f2b1e7f14d1abeb0fa2d4ba3894c69a1583
+  metadata.gz: f4fd3f8f12a3fb32891d97e33879626fa74968ef7dc42b6c776719050403d2ab
+  data.tar.gz: 12bca7ef36e1c8b70d3a9a90203e8571fdd6f326feb59b1cb83dde8dac81eca2
 SHA512:
-  metadata.gz: df70fd2fd900ef438d5da6bf972037cc1fce126a24664b86836375ad44462f65f6e48d2cb0f32bb5fd047241e7bdf9abc6d4a293c2a24796fb097a5406158b33
-  data.tar.gz: 1b6fac487796259adc81a0e9f83ee946a7973cab84d7297a4f4f0a0c8e743aaa65c9ea5a852f1620590dcca182538ca71a13c4dbc74c62975940099df4def133
+  metadata.gz: 0d213ff3b27c639fcd4595c7fa0ff033c40d5b0a63efa0f9e97ea6c4021a8b524e3130da971c0152324877c827e6aeb091797cc49d5a14011d44b5fe13f89ab0
+  data.tar.gz: c2d43976c66b990c24f631d25d24ae8aa5885a2e903701ef06a61de96a35a470b502da8fec8d00a99910b65d1165d4c02d396a49dbfc1205f3a3ee348fa2868d

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    dropbox-sign (1.4.0)
+    dropbox-sign (1.4.1)
       typhoeus (~> 1.0, >= 1.0.1)
 
 GEM
@@ -13,7 +13,10 @@ GEM
     diff-lcs (1.5.0)
     ethon (0.16.0)
       ffi (>= 1.15.0)
-    ffi (1.16.3)
+    ffi (1.17.0-aarch64-linux-gnu)
+    ffi (1.17.0-arm64-darwin)
+    ffi (1.17.0-x86_64-darwin)
+    ffi (1.17.0-x86_64-linux-gnu)
     jaro_winkler (1.5.4)
     json_spec (1.1.5)
       multi_json (~> 1.0)

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.4.0
+- Package version: 1.4.1
 - Build package: org.openapitools.codegen.languages.RubyClientCodegen
 
 ## Installation
@@ -46,14 +46,14 @@ gem build dropbox-sign.gemspec
 Then install the gem locally:
 
 ```shell
-gem install ./dropbox-sign-1.4.0.gem
+gem install ./dropbox-sign-1.4.1.gem
 ```
 
-(for development, run `gem install --dev ./dropbox-sign-1.4.0.gem` to install the development dependencies)
+(for development, run `gem install --dev ./dropbox-sign-1.4.1.gem` to install the development dependencies)
 
 Finally add this to the Gemfile:
 
-    gem 'dropbox-sign', '~> 1.4.0'
+    gem 'dropbox-sign', '~> 1.4.1'
 
 ### Install from Git
 
@@ -127,10 +127,6 @@ All URIs are relative to *https://api.hellosign.com/v3*
 |*Dropbox::Sign::SignatureRequestApi* | [**signature_request_cancel**](docs/SignatureRequestApi.md#signature_request_cancel) | **POST** /signature_request/cancel/{signature_request_id} | Cancel Incomplete Signature Request |
 |*Dropbox::Sign::SignatureRequestApi* | [**signature_request_create_embedded**](docs/SignatureRequestApi.md#signature_request_create_embedded) | **POST** /signature_request/create_embedded | Create Embedded Signature Request |
 |*Dropbox::Sign::SignatureRequestApi* | [**signature_request_create_embedded_with_template**](docs/SignatureRequestApi.md#signature_request_create_embedded_with_template) | **POST** /signature_request/create_embedded_with_template | Create Embedded Signature Request with Template |
-|*Dropbox::Sign::SignatureRequestApi* | [**signature_request_edit**](docs/SignatureRequestApi.md#signature_request_edit) | **PUT** /signature_request/edit/{signature_request_id} | Edit Signature Request |
-|*Dropbox::Sign::SignatureRequestApi* | [**signature_request_edit_embedded**](docs/SignatureRequestApi.md#signature_request_edit_embedded) | **PUT** /signature_request/edit_embedded/{signature_request_id} | Edit Embedded Signature Request |
-|*Dropbox::Sign::SignatureRequestApi* | [**signature_request_edit_embedded_with_template**](docs/SignatureRequestApi.md#signature_request_edit_embedded_with_template) | **PUT** /signature_request/edit_embedded_with_template/{signature_request_id} | Edit Embedded Signature Request with Template |
-|*Dropbox::Sign::SignatureRequestApi* | [**signature_request_edit_with_template**](docs/SignatureRequestApi.md#signature_request_edit_with_template) | **PUT** /signature_request/edit_with_template/{signature_request_id} | Edit Signature Request With Template |
 |*Dropbox::Sign::SignatureRequestApi* | [**signature_request_files**](docs/SignatureRequestApi.md#signature_request_files) | **GET** /signature_request/files/{signature_request_id} | Download Files |
 |*Dropbox::Sign::SignatureRequestApi* | [**signature_request_files_as_data_uri**](docs/SignatureRequestApi.md#signature_request_files_as_data_uri) | **GET** /signature_request/files_as_data_uri/{signature_request_id} | Download Files as Data Uri |
 |*Dropbox::Sign::SignatureRequestApi* | [**signature_request_files_as_file_url**](docs/SignatureRequestApi.md#signature_request_files_as_file_url) | **GET** /signature_request/files_as_file_url/{signature_request_id} | Download Files as File Url |
@@ -217,10 +213,6 @@ All URIs are relative to *https://api.hellosign.com/v3*
  - [Dropbox::Sign::SignatureRequestBulkSendWithTemplateRequest](docs/SignatureRequestBulkSendWithTemplateRequest.md)
  - [Dropbox::Sign::SignatureRequestCreateEmbeddedRequest](docs/SignatureRequestCreateEmbeddedRequest.md)
  - [Dropbox::Sign::SignatureRequestCreateEmbeddedWithTemplateRequest](docs/SignatureRequestCreateEmbeddedWithTemplateRequest.md)
- - [Dropbox::Sign::SignatureRequestEditEmbeddedRequest](docs/SignatureRequestEditEmbeddedRequest.md)
- - [Dropbox::Sign::SignatureRequestEditEmbeddedWithTemplateRequest](docs/SignatureRequestEditEmbeddedWithTemplateRequest.md)
- - [Dropbox::Sign::SignatureRequestEditRequest](docs/SignatureRequestEditRequest.md)
- - [Dropbox::Sign::SignatureRequestEditWithTemplateRequest](docs/SignatureRequestEditWithTemplateRequest.md)
  - [Dropbox::Sign::SignatureRequestGetResponse](docs/SignatureRequestGetResponse.md)
  - [Dropbox::Sign::SignatureRequestListResponse](docs/SignatureRequestListResponse.md)
  - [Dropbox::Sign::SignatureRequestRemindRequest](docs/SignatureRequestRemindRequest.md)

data/VERSION

@@ -1 +1 @@
-1.4.0
+1.4.1

data/docs/EmbeddedEditUrlRequest.md

@@ -12,7 +12,7 @@
 | `force_signer_roles` | ```Boolean``` |  Provide users the ability to review/edit the template signer roles.  |  [default to false] |
 | `force_subject_message` | ```Boolean``` |  Provide users the ability to review/edit the template subject and message.  |  [default to false] |
 | `merge_fields` | [```Array<SubMergeField>```](SubMergeField.md) |  Add additional merge fields to the template, which can be used used to pre-fill data by passing values into signature requests made with that template.<br><br>Remove all merge fields on the template by passing an empty array `[]`.  |  |
-| `preview_only` | ```Boolean``` |  This allows the requester to enable the preview experience (i.e. does not allow the requester&#39;s end user to add any additional fields via the editor).<br><br>**Note**: This parameter overwrites `show_preview&#x3D;true` (if set).  |  [default to false] |
+| `preview_only` | ```Boolean``` |  This allows the requester to enable the preview experience (i.e. does not allow the requester&#39;s end user to add any additional fields via the editor).<br><br>**NOTE:** This parameter overwrites `show_preview&#x3D;true` (if set).  |  [default to false] |
 | `show_preview` | ```Boolean``` |  This allows the requester to enable the editor/preview experience.  |  [default to false] |
 | `show_progress_stepper` | ```Boolean``` |  When only one step remains in the signature request process and this parameter is set to `false` then the progress stepper will be hidden.  |  [default to true] |
 | `test_mode` | ```Boolean``` |  Whether this is a test, locked templates will only be available for editing if this is set to `true`. Defaults to `false`.  |  [default to false] |

data/docs/SignatureRequestApi.md

@@ -9,10 +9,6 @@ All URIs are relative to *https://api.hellosign.com/v3*
 | [`signature_request_cancel`](SignatureRequestApi.md#signature_request_cancel) | **POST** `/signature_request/cancel/{signature_request_id}` | Cancel Incomplete Signature Request |
 | [`signature_request_create_embedded`](SignatureRequestApi.md#signature_request_create_embedded) | **POST** `/signature_request/create_embedded` | Create Embedded Signature Request |
 | [`signature_request_create_embedded_with_template`](SignatureRequestApi.md#signature_request_create_embedded_with_template) | **POST** `/signature_request/create_embedded_with_template` | Create Embedded Signature Request with Template |
-| [`signature_request_edit`](SignatureRequestApi.md#signature_request_edit) | **PUT** `/signature_request/edit/{signature_request_id}` | Edit Signature Request |
-| [`signature_request_edit_embedded`](SignatureRequestApi.md#signature_request_edit_embedded) | **PUT** `/signature_request/edit_embedded/{signature_request_id}` | Edit Embedded Signature Request |
-| [`signature_request_edit_embedded_with_template`](SignatureRequestApi.md#signature_request_edit_embedded_with_template) | **PUT** `/signature_request/edit_embedded_with_template/{signature_request_id}` | Edit Embedded Signature Request with Template |
-| [`signature_request_edit_with_template`](SignatureRequestApi.md#signature_request_edit_with_template) | **PUT** `/signature_request/edit_with_template/{signature_request_id}` | Edit Signature Request With Template |
 | [`signature_request_files`](SignatureRequestApi.md#signature_request_files) | **GET** `/signature_request/files/{signature_request_id}` | Download Files |
 | [`signature_request_files_as_data_uri`](SignatureRequestApi.md#signature_request_files_as_data_uri) | **GET** `/signature_request/files_as_data_uri/{signature_request_id}` | Download Files as Data Uri |
 | [`signature_request_files_as_file_url`](SignatureRequestApi.md#signature_request_files_as_file_url) | **GET** `/signature_request/files_as_file_url/{signature_request_id}` | Download Files as File Url |
@@ -32,7 +28,7 @@ All URIs are relative to *https://api.hellosign.com/v3*
 
 Embedded Bulk Send with Template
 
-Creates BulkSendJob which sends up to 250 SignatureRequests in bulk based off of the provided Template(s) specified with the `template_ids` parameter to be signed in an embedded iFrame. These embedded signature requests can only be signed in embedded iFrames whereas normal signature requests can only be signed on Dropbox Sign.  **NOTE**: Only available for Standard plan and higher.
+Creates BulkSendJob which sends up to 250 SignatureRequests in bulk based off of the provided Template(s) specified with the `template_ids` parameter to be signed in an embedded iFrame. These embedded signature requests can only be signed in embedded iFrames whereas normal signature requests can only be signed on Dropbox Sign.  **NOTE:** Only available for Standard plan and higher.
 
 ### Examples
 
@@ -143,7 +139,7 @@ end
 
 Bulk Send with Template
 
-Creates BulkSendJob which sends up to 250 SignatureRequests in bulk based off of the provided Template(s) specified with the `template_ids` parameter.  **NOTE**: Only available for Standard plan and higher.
+Creates BulkSendJob which sends up to 250 SignatureRequests in bulk based off of the provided Template(s) specified with the `template_ids` parameter.  **NOTE:** Only available for Standard plan and higher.
 
 ### Examples
 
@@ -253,7 +249,7 @@ end
 
 Cancel Incomplete Signature Request
 
-Cancels an incomplete signature request. This action is **not reversible**.  The request will be canceled and signers will no longer be able to sign. If they try to access the signature request they will receive a HTTP 410 status code indicating that the resource has been deleted. Cancelation is asynchronous and a successful call to this endpoint will return an empty 200 OK response if the signature request is eligible to be canceled and has been successfully queued.  This 200 OK response does not indicate a successful cancelation of the signature request itself. The cancelation is confirmed via the `signature_request_canceled` event. It is recommended that a  [callback handler](/api/reference/tag/Callbacks-and-Events) be implemented to listen for the `signature_request_canceled` event. This callback will be sent only when the cancelation has completed successfully. 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](https://app.hellosign.com/apidashboard) and retry the cancelation if necessary.  To be eligible for cancelation, a signature request must have been sent successfully, must not yet have been signed by all signers, and you must either be the sender or own the API app under which it was sent. A partially signed signature request can be canceled.  **NOTE**: To remove your access to a completed signature request, use the endpoint: `POST /signature_request/remove/[:signature_request_id]`.
+Cancels an incomplete signature request. This action is **not reversible**.  The request will be canceled and signers will no longer be able to sign. If they try to access the signature request they will receive a HTTP 410 status code indicating that the resource has been deleted. Cancelation is asynchronous and a successful call to this endpoint will return an empty 200 OK response if the signature request is eligible to be canceled and has been successfully queued.  This 200 OK response does not indicate a successful cancelation of the signature request itself. The cancelation is confirmed via the `signature_request_canceled` event. It is recommended that a  [callback handler](/api/reference/tag/Callbacks-and-Events) be implemented to listen for the `signature_request_canceled` event. This callback will be sent only when the cancelation has completed successfully. 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](https://app.hellosign.com/apidashboard) and retry the cancelation if necessary.  To be eligible for cancelation, a signature request must have been sent successfully, must not yet have been signed by all signers, and you must either be the sender or own the API app under which it was sent. A partially signed signature request can be canceled.  **NOTE:** To remove your access to a completed signature request, use the endpoint: `POST /signature_request/remove/[:signature_request_id]`.
 
 ### Examples
 
@@ -325,7 +321,7 @@ nil (empty response body)
 
 Create Embedded Signature Request
 
-Creates a new SignatureRequest with the submitted documents to be signed in an embedded iFrame. If form_fields_per_document is not specified, a signature page will be affixed where all signers will be required to add their signature, signifying their agreement to all contained documents. <u>Note</u> that embedded signature requests can only be signed in embedded iFrames whereas normal signature requests can only be signed on Dropbox Sign.
+Creates a new SignatureRequest with the submitted documents to be signed in an embedded iFrame. If form_fields_per_document is not specified, a signature page will be affixed where all signers will be required to add their signature, signifying their agreement to all contained documents. Note that embedded signature requests can only be signed in embedded iFrames whereas normal signature requests can only be signed on Dropbox Sign.
 
 ### Examples
 
@@ -423,7 +419,7 @@ end
 
 Create Embedded Signature Request with Template
 
-Creates a new SignatureRequest based on the given Template(s) to be signed in an embedded iFrame. <u>Note</u> that embedded signature requests can only be signed in embedded iFrames whereas normal signature requests can only be signed on Dropbox Sign.
+Creates a new SignatureRequest based on the given Template(s) to be signed in an embedded iFrame. Note that embedded signature requests can only be signed in embedded iFrames whereas normal signature requests can only be signed on Dropbox Sign.
 
 ### Examples
 
@@ -508,417 +504,6 @@ end
 - **Accept**: application/json
 
 
-## `signature_request_edit`
-
-> `<SignatureRequestGetResponse> signature_request_edit(signature_request_id, signature_request_edit_request)`
-
-Edit Signature Request
-
-Edits and sends a SignatureRequest with the submitted documents. If `form_fields_per_document` is not specified, a signature page will be affixed where all signers will be required to add their signature, signifying their agreement to all contained documents.  **NOTE:** Edit and resend will not deduct your signature request quota.
-
-### Examples
-
-```ruby
-require "dropbox-sign"
-
-Dropbox::Sign.configure do |config|
-  # Configure HTTP basic authorization: api_key
-  config.username = "YOUR_API_KEY"
-
-  # or, configure Bearer (JWT) authorization: oauth2
-  # config.access_token = "YOUR_ACCESS_TOKEN"
-end
-
-signature_request_api = Dropbox::Sign::SignatureRequestApi.new
-
-signer_1 = Dropbox::Sign::SubSignatureRequestSigner.new
-signer_1.email_address = "jack@example.com"
-signer_1.name = "Jack"
-signer_1.order = 0
-
-signer_2 = Dropbox::Sign::SubSignatureRequestSigner.new
-signer_2.email_address = "jill@example.com"
-signer_2.name = "Jill"
-signer_2.order = 1
-
-signing_options = Dropbox::Sign::SubSigningOptions.new
-signing_options.draw = true
-signing_options.type = true
-signing_options.upload = true
-signing_options.phone = true
-signing_options.default_type = "draw"
-
-field_options = Dropbox::Sign::SubFieldOptions.new
-field_options.date_format = "DD - MM - YYYY"
-
-data = Dropbox::Sign::SignatureRequestEditRequest.new
-data.title = "NDA with Acme Co."
-data.subject = "The NDA we talked about"
-data.message = "Please sign this NDA and then we can discuss more. Let me know if you have any questions."
-data.signers = [signer_1, signer_2]
-data.cc_email_addresses = [
-  "lawyer1@dropboxsign.com",
-  "lawyer2@dropboxsign.com",
-]
-data.files = [File.new("example_signature_request.pdf", "r")]
-data.metadata = {
-  custom_id: 1234,
-  custom_text: "NDA #9",
-}
-data.signing_options = signing_options
-data.field_options = field_options
-data.test_mode = true
-
-signature_request_id = "2f9781e1a8e2045224d808c153c2e1d3df6f8f2f"
-
-begin
-  result = signature_request_api.signature_request_edit(signature_request_id, data)
-  p result
-rescue Dropbox::Sign::ApiError => e
-  puts "Exception when calling Dropbox Sign API: #{e}"
-end
-
-```
-
-#### Using the `signature_request_edit_with_http_info` variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> `<Array(<SignatureRequestGetResponse>, Integer, Hash)> signature_request_edit_with_http_info(signature_request_id, signature_request_edit_request)`
-
-```ruby
-begin
-  # Edit Signature Request
-  data, status_code, headers = api_instance.signature_request_edit_with_http_info(signature_request_id, signature_request_edit_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <SignatureRequestGetResponse>
-rescue Dropbox::Sign::ApiError => e
-  puts "Error when calling SignatureRequestApi->signature_request_edit_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| `signature_request_id` | **String** | The id of the SignatureRequest to edit. |  |
-| `signature_request_edit_request` | [**SignatureRequestEditRequest**](SignatureRequestEditRequest.md) |  |  |
-
-### Return type
-
-[**SignatureRequestGetResponse**](SignatureRequestGetResponse.md)
-
-### Authorization
-
-[api_key](../README.md#api_key), [oauth2](../README.md#oauth2)
-
-### HTTP request headers
-
-- **Content-Type**: application/json, multipart/form-data
-- **Accept**: application/json
-
-
-## `signature_request_edit_embedded`
-
-> `<SignatureRequestGetResponse> signature_request_edit_embedded(signature_request_id, signature_request_edit_embedded_request)`
-
-Edit Embedded Signature Request
-
-Edits a SignatureRequest with the submitted documents to be signed in an embedded iFrame. If form_fields_per_document is not specified, a signature page will be affixed where all signers will be required to add their signature, signifying their agreement to all contained documents. <u>Note</u> that embedded signature requests can only be signed in embedded iFrames whereas normal signature requests can only be signed on Dropbox Sign.
-
-### Examples
-
-```ruby
-require "dropbox-sign"
-
-Dropbox::Sign.configure do |config|
-  # Configure HTTP basic authorization: api_key
-  config.username = "YOUR_API_KEY"
-
-  # or, configure Bearer (JWT) authorization: oauth2
-  # config.access_token = "YOUR_ACCESS_TOKEN"
-end
-
-signature_request_api = Dropbox::Sign::SignatureRequestApi.new
-
-signer_1 = Dropbox::Sign::SubSignatureRequestSigner.new
-signer_1.email_address = "jack@example.com"
-signer_1.name = "Jack"
-signer_1.order = 0
-
-signer_2 = Dropbox::Sign::SubSignatureRequestSigner.new
-signer_2.email_address = "jill@example.com"
-signer_2.name = "Jill"
-signer_2.order = 1
-
-signing_options = Dropbox::Sign::SubSigningOptions.new
-signing_options.draw = true
-signing_options.type = true
-signing_options.upload = true
-signing_options.phone = true
-signing_options.default_type = "draw"
-
-data = Dropbox::Sign::SignatureRequestEditEmbeddedRequest.new
-data.client_id = "ec64a202072370a737edf4a0eb7f4437"
-data.title = "NDA with Acme Co."
-data.subject = "The NDA we talked about"
-data.message = "Please sign this NDA and then we can discuss more. Let me know if you have any questions."
-data.signers = [signer_1, signer_2]
-data.cc_email_addresses = ["lawyer1@dropboxsign.com", "lawyer2@dropboxsign.com"]
-data.files = [File.new("example_signature_request.pdf", "r")]
-data.signing_options = signing_options
-data.test_mode = true
-
-signature_request_id = "2f9781e1a8e2045224d808c153c2e1d3df6f8f2f"
-
-begin
-  result = signature_request_api.signature_request_edit_embedded(signature_request_id, data)
-  p result
-rescue Dropbox::Sign::ApiError => e
-  puts "Exception when calling Dropbox Sign API: #{e}"
-end
-
-```
-
-#### Using the `signature_request_edit_embedded_with_http_info` variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> `<Array(<SignatureRequestGetResponse>, Integer, Hash)> signature_request_edit_embedded_with_http_info(signature_request_id, signature_request_edit_embedded_request)`
-
-```ruby
-begin
-  # Edit Embedded Signature Request
-  data, status_code, headers = api_instance.signature_request_edit_embedded_with_http_info(signature_request_id, signature_request_edit_embedded_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <SignatureRequestGetResponse>
-rescue Dropbox::Sign::ApiError => e
-  puts "Error when calling SignatureRequestApi->signature_request_edit_embedded_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| `signature_request_id` | **String** | The id of the SignatureRequest to edit. |  |
-| `signature_request_edit_embedded_request` | [**SignatureRequestEditEmbeddedRequest**](SignatureRequestEditEmbeddedRequest.md) |  |  |
-
-### Return type
-
-[**SignatureRequestGetResponse**](SignatureRequestGetResponse.md)
-
-### Authorization
-
-[api_key](../README.md#api_key), [oauth2](../README.md#oauth2)
-
-### HTTP request headers
-
-- **Content-Type**: application/json, multipart/form-data
-- **Accept**: application/json
-
-
-## `signature_request_edit_embedded_with_template`
-
-> `<SignatureRequestGetResponse> signature_request_edit_embedded_with_template(signature_request_id, signature_request_edit_embedded_with_template_request)`
-
-Edit Embedded Signature Request with Template
-
-Edits a SignatureRequest based on the given Template(s) to be signed in an embedded iFrame. <u>Note</u> that embedded signature requests can only be signed in embedded iFrames whereas normal signature requests can only be signed on Dropbox Sign.
-
-### Examples
-
-```ruby
-require "dropbox-sign"
-
-Dropbox::Sign.configure do |config|
-  # Configure HTTP basic authorization: api_key
-  config.username = "YOUR_API_KEY"
-
-  # or, configure Bearer (JWT) authorization: oauth2
-  # config.access_token = "YOUR_ACCESS_TOKEN"
-end
-
-signature_request_api = Dropbox::Sign::SignatureRequestApi.new
-
-signer_1 = Dropbox::Sign::SubSignatureRequestTemplateSigner.new
-signer_1.role = "Client"
-signer_1.email_address = "jack@example.com"
-signer_1.name = "Jack"
-
-signing_options = Dropbox::Sign::SubSigningOptions.new
-signing_options.draw = true
-signing_options.type = true
-signing_options.upload = true
-signing_options.phone = true
-signing_options.default_type = "draw"
-
-data = Dropbox::Sign::SignatureRequestEditEmbeddedWithTemplateRequest.new
-data.client_id = "ec64a202072370a737edf4a0eb7f4437"
-data.template_ids = ["c26b8a16784a872da37ea946b9ddec7c1e11dff6"]
-data.subject = "Purchase Order"
-data.message = "Glad we could come to an agreement."
-data.signers = [signer_1]
-data.signing_options = signing_options
-data.test_mode = true
-
-signature_request_id = "2f9781e1a8e2045224d808c153c2e1d3df6f8f2f"
-
-begin
-  result = signature_request_api.signature_request_edit_embedded_with_template(signature_request_id, data)
-  p result
-rescue Dropbox::Sign::ApiError => e
-  puts "Exception when calling Dropbox Sign API: #{e}"
-end
-
-```
-
-#### Using the `signature_request_edit_embedded_with_template_with_http_info` variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> `<Array(<SignatureRequestGetResponse>, Integer, Hash)> signature_request_edit_embedded_with_template_with_http_info(signature_request_id, signature_request_edit_embedded_with_template_request)`
-
-```ruby
-begin
-  # Edit Embedded Signature Request with Template
-  data, status_code, headers = api_instance.signature_request_edit_embedded_with_template_with_http_info(signature_request_id, signature_request_edit_embedded_with_template_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <SignatureRequestGetResponse>
-rescue Dropbox::Sign::ApiError => e
-  puts "Error when calling SignatureRequestApi->signature_request_edit_embedded_with_template_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| `signature_request_id` | **String** | The id of the SignatureRequest to edit. |  |
-| `signature_request_edit_embedded_with_template_request` | [**SignatureRequestEditEmbeddedWithTemplateRequest**](SignatureRequestEditEmbeddedWithTemplateRequest.md) |  |  |
-
-### Return type
-
-[**SignatureRequestGetResponse**](SignatureRequestGetResponse.md)
-
-### Authorization
-
-[api_key](../README.md#api_key), [oauth2](../README.md#oauth2)
-
-### HTTP request headers
-
-- **Content-Type**: application/json, multipart/form-data
-- **Accept**: application/json
-
-
-## `signature_request_edit_with_template`
-
-> `<SignatureRequestGetResponse> signature_request_edit_with_template(signature_request_id, signature_request_edit_with_template_request)`
-
-Edit Signature Request With Template
-
-Edits and sends a SignatureRequest based off of the Template(s) specified with the template_ids parameter.  **NOTE:** Edit and resend will not deduct your signature request quota.
-
-### Examples
-
-```ruby
-require "dropbox-sign"
-
-Dropbox::Sign.configure do |config|
-  # Configure HTTP basic authorization: api_key
-  config.username = "YOUR_API_KEY"
-
-  # or, configure Bearer (JWT) authorization: oauth2
-  # config.access_token = "YOUR_ACCESS_TOKEN"
-end
-
-signature_request_api = Dropbox::Sign::SignatureRequestApi.new
-
-signer_1 = Dropbox::Sign::SubSignatureRequestTemplateSigner.new
-signer_1.role = "Client"
-signer_1.email_address = "george@example.com"
-signer_1.name = "George"
-
-cc_1 = Dropbox::Sign::SubCC.new
-cc_1.role = "Accounting"
-cc_1.email_address = "accounting@example.com"
-
-custom_field_1 = Dropbox::Sign::SubCustomField.new
-custom_field_1.name = "Cost"
-custom_field_1.value = "$20,000"
-custom_field_1.editor = "Client"
-custom_field_1.required = true
-
-signing_options = Dropbox::Sign::SubSigningOptions.new
-signing_options.draw = true
-signing_options.type = true
-signing_options.upload = true
-signing_options.phone = false
-signing_options.default_type = "draw"
-
-data = Dropbox::Sign::SignatureRequestSendWithTemplateRequest.new
-data.template_ids = ["c26b8a16784a872da37ea946b9ddec7c1e11dff6"]
-data.subject = "Purchase Order"
-data.message = "Glad we could come to an agreement."
-data.signers = [signer_1]
-data.ccs = [cc_1]
-data.custom_fields = [custom_field_1]
-data.signing_options = signing_options
-data.test_mode = true
-
-signature_request_id = "2f9781e1a8e2045224d808c153c2e1d3df6f8f2f"
-
-begin
-  result = signature_request_api.signature_request_edit_with_template(signature_request_id, data)
-  p result
-rescue Dropbox::Sign::ApiError => e
-  puts "Exception when calling Dropbox Sign API: #{e}"
-end
-
-```
-
-#### Using the `signature_request_edit_with_template_with_http_info` variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> `<Array(<SignatureRequestGetResponse>, Integer, Hash)> signature_request_edit_with_template_with_http_info(signature_request_id, signature_request_edit_with_template_request)`
-
-```ruby
-begin
-  # Edit Signature Request With Template
-  data, status_code, headers = api_instance.signature_request_edit_with_template_with_http_info(signature_request_id, signature_request_edit_with_template_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <SignatureRequestGetResponse>
-rescue Dropbox::Sign::ApiError => e
-  puts "Error when calling SignatureRequestApi->signature_request_edit_with_template_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| `signature_request_id` | **String** | The id of the SignatureRequest to edit. |  |
-| `signature_request_edit_with_template_request` | [**SignatureRequestEditWithTemplateRequest**](SignatureRequestEditWithTemplateRequest.md) |  |  |
-
-### Return type
-
-[**SignatureRequestGetResponse**](SignatureRequestGetResponse.md)
-
-### Authorization
-
-[api_key](../README.md#api_key), [oauth2](../README.md#oauth2)
-
-### HTTP request headers
-
-- **Content-Type**: application/json, multipart/form-data
-- **Accept**: application/json
-
-
 ## `signature_request_files`
 
 > `File signature_request_files(signature_request_id, opts)`
@@ -1363,7 +948,7 @@ end
 
 Send Request Reminder
 
-Sends an email to the signer reminding them to sign the signature request. You cannot send a reminder within 1 hour of the last reminder that was sent. This includes manual AND automatic reminders.  **NOTE**: This action can **not** be used with embedded signature requests.
+Sends an email to the signer reminding them to sign the signature request. You cannot send a reminder within 1 hour of the last reminder that was sent. This includes manual AND automatic reminders.  **NOTE:** This action can **not** be used with embedded signature requests.
 
 ### Examples
 
@@ -1721,7 +1306,7 @@ end
 
 Update Signature Request
 
-Updates the email address and/or the name for a given signer on a signature request. You can listen for the `signature_request_email_bounce` event on your app or account to detect bounced emails, and respond with this method.  Updating the email address of a signer will generate a new `signature_id` value.  **NOTE**: This action cannot be performed on a signature request with an appended signature page.
+Updates the email address and/or the name for a given signer on a signature request. You can listen for the `signature_request_email_bounce` event on your app or account to detect bounced emails, and respond with this method.  Updating the email address of a signer will generate a new `signature_id` value.  **NOTE:** This action cannot be performed on a signature request with an appended signature page.
 
 ### Examples
 

data/docs/SignatureRequestBulkCreateEmbeddedWithTemplateRequest.md

@@ -8,7 +8,7 @@
 | ---- | ---- | ----------- | ----- |
 | `template_ids`<sup>*_required_</sup> | ```Array<String>``` |  Use `template_ids` to create a SignatureRequest from one or more templates, in the order in which the template will be used.  |  |
 | `client_id`<sup>*_required_</sup> | ```String``` |  Client id of the app you&#39;re using to create this embedded signature request. Used for security purposes.  |  |
-| `signer_file` | ```File``` |  `signer_file` is a CSV file defining values and options for signer fields. Required unless a `signer_list` is used, you may not use both. The CSV can have the following columns:<br><br>- `name`: the name of the signer filling the role of RoleName - `email_address`: email address of the signer filling the role of RoleName - `pin`: the 4- to 12-character access code that will secure this signer&#39;s signature page (optional) - `sms_phone_number`: An E.164 formatted phone number that will receive a code via SMS to access this signer&#39;s signature page. (optional)<br><br>    By using the feature, you agree you are responsible for obtaining a signer&#39;s consent to receive text messages from Dropbox Sign related to this signature request and confirm you have obtained such consent from all signers prior to enabling SMS delivery for this signature request. [Learn more](https://faq.hellosign.com/hc/en-us/articles/15815316468877-Dropbox-Sign-SMS-tools-add-on).<br><br>    **Note**: Not available in test mode and requires a Standard plan or higher. - `*_field`: any column with a _field&quot; suffix will be treated as a custom field (optional)<br><br>    You may only specify field values here, any other options should be set in the custom_fields request parameter.<br><br>Example CSV:<br><br>``` name, email_address, pin, company_field George, george@example.com, d79a3td, ABC Corp Mary, mary@example.com, gd9as5b, 123 LLC ```  |  |
+| `signer_file` | ```File``` |  `signer_file` is a CSV file defining values and options for signer fields. Required unless a `signer_list` is used, you may not use both. The CSV can have the following columns:<br><br>- `name`: the name of the signer filling the role of RoleName - `email_address`: email address of the signer filling the role of RoleName - `pin`: the 4- to 12-character access code that will secure this signer&#39;s signature page (optional) - `sms_phone_number`: An E.164 formatted phone number that will receive a code via SMS to access this signer&#39;s signature page. (optional)<br><br>    By using the feature, you agree you are responsible for obtaining a signer&#39;s consent to receive text messages from Dropbox Sign related to this signature request and confirm you have obtained such consent from all signers prior to enabling SMS delivery for this signature request. [Learn more](https://faq.hellosign.com/hc/en-us/articles/15815316468877-Dropbox-Sign-SMS-tools-add-on).<br><br>    **NOTE:** Not available in test mode and requires a Standard plan or higher. - `*_field`: any column with a _field&quot; suffix will be treated as a custom field (optional)<br><br>    You may only specify field values here, any other options should be set in the custom_fields request parameter.<br><br>Example CSV:<br><br>``` name, email_address, pin, company_field George, george@example.com, d79a3td, ABC Corp Mary, mary@example.com, gd9as5b, 123 LLC ```  |  |
 | `signer_list` | [```Array<SubBulkSignerList>```](SubBulkSignerList.md) |  `signer_list` is an array defining values and options for signer fields. Required unless a `signer_file` is used, you may not use both.  |  |
 | `allow_decline` | ```Boolean``` |  Allows signers to decline to sign a document if `true`. Defaults to `false`.  |  [default to false] |
 | `ccs` | [```Array<SubCC>```](SubCC.md) |  Add CC email recipients. Required when a CC role exists for the Template.  |  |

data/docs/SignatureRequestBulkSendWithTemplateRequest.md

@@ -7,7 +7,7 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | `template_ids`<sup>*_required_</sup> | ```Array<String>``` |  Use `template_ids` to create a SignatureRequest from one or more templates, in the order in which the template will be used.  |  |
-| `signer_file` | ```File``` |  `signer_file` is a CSV file defining values and options for signer fields. Required unless a `signer_list` is used, you may not use both. The CSV can have the following columns:<br><br>- `name`: the name of the signer filling the role of RoleName - `email_address`: email address of the signer filling the role of RoleName - `pin`: the 4- to 12-character access code that will secure this signer&#39;s signature page (optional) - `sms_phone_number`: An E.164 formatted phone number that will receive a code via SMS to access this signer&#39;s signature page. (optional)<br><br>    By using the feature, you agree you are responsible for obtaining a signer&#39;s consent to receive text messages from Dropbox Sign related to this signature request and confirm you have obtained such consent from all signers prior to enabling SMS delivery for this signature request. [Learn more](https://faq.hellosign.com/hc/en-us/articles/15815316468877-Dropbox-Sign-SMS-tools-add-on).<br><br>    **Note**: Not available in test mode and requires a Standard plan or higher. - `*_field`: any column with a _field&quot; suffix will be treated as a custom field (optional)<br><br>    You may only specify field values here, any other options should be set in the custom_fields request parameter.<br><br>Example CSV:<br><br>``` name, email_address, pin, company_field George, george@example.com, d79a3td, ABC Corp Mary, mary@example.com, gd9as5b, 123 LLC ```  |  |
+| `signer_file` | ```File``` |  `signer_file` is a CSV file defining values and options for signer fields. Required unless a `signer_list` is used, you may not use both. The CSV can have the following columns:<br><br>- `name`: the name of the signer filling the role of RoleName - `email_address`: email address of the signer filling the role of RoleName - `pin`: the 4- to 12-character access code that will secure this signer&#39;s signature page (optional) - `sms_phone_number`: An E.164 formatted phone number that will receive a code via SMS to access this signer&#39;s signature page. (optional)<br><br>    By using the feature, you agree you are responsible for obtaining a signer&#39;s consent to receive text messages from Dropbox Sign related to this signature request and confirm you have obtained such consent from all signers prior to enabling SMS delivery for this signature request. [Learn more](https://faq.hellosign.com/hc/en-us/articles/15815316468877-Dropbox-Sign-SMS-tools-add-on).<br><br>    **NOTE:** Not available in test mode and requires a Standard plan or higher. - `*_field`: any column with a _field&quot; suffix will be treated as a custom field (optional)<br><br>    You may only specify field values here, any other options should be set in the custom_fields request parameter.<br><br>Example CSV:<br><br>``` name, email_address, pin, company_field George, george@example.com, d79a3td, ABC Corp Mary, mary@example.com, gd9as5b, 123 LLC ```  |  |
 | `signer_list` | [```Array<SubBulkSignerList>```](SubBulkSignerList.md) |  `signer_list` is an array defining values and options for signer fields. Required unless a `signer_file` is used, you may not use both.  |  |
 | `allow_decline` | ```Boolean``` |  Allows signers to decline to sign a document if `true`. Defaults to `false`.  |  [default to false] |
 | `ccs` | [```Array<SubCC>```](SubCC.md) |  Add CC email recipients. Required when a CC role exists for the Template.  |  |