dropbox-sign 1.0.0.pre.beta2301 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4b162ad2b35753ad7b7d5990f3d5d1e212af25ede33c4f0aca2eae13c0490d34
-  data.tar.gz: e65432eebd4f3baa8131e3b2e37eb75c559d5487b586c78cc9ec7ec935cbbbf3
+  metadata.gz: 5cd9c2abe6acfbf4366ab760fe1eb3dfc94f79c75fce22c6d83e0112ef56431a
+  data.tar.gz: 3bc5f3fb30ccf70c05ba6836dc91bfa6aaa77e9e7867138c5d77bbf3868820c4
 SHA512:
-  metadata.gz: 3cdf1579d3fcecf69af52bc66f3a2681f297b675c0dfeaedc906cc253436b7af177a90cc3b54c552a960221ecde576b928efb840d99baf61f53c939050a616e7
-  data.tar.gz: 7f7c81cdb0b600fafe69baa4d8287e687152691dd733c0f179e887a95b741512d02cf8949e9805ba064de039f0a91eac372902dfa0120bcc4dd5b03c1002db79
+  metadata.gz: 20cec127dfa5530e7e52048d540729675586ef0c7d4698bc57353b62dee0a8eda3a8a6b95207d05dcd145b43dd2583749d93e6b78729a3b49a7070b0e271f10e
+  data.tar.gz: fdb5a6cd0d8b0bd8b40542548e6e38484fdad170ddebe24493f330174f9faea0c84df482b5b71dc36706df1b7fc1544c487b63ccd38e4588067d96bd03dedb47

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    dropbox-sign (1.0.0.pre.beta2301)
+    dropbox-sign (1.0.1)
       typhoeus (~> 1.0, >= 1.0.1)
 
 GEM

data/README.md

@@ -6,7 +6,7 @@ Dropbox Sign v3 API
 
 ## Migrating from legacy SDK
 
-This SDK is generated from our officially maintained [OpenAPI spec](https://github.com/hellosign/hellosign-openapi/blob/development/openapi.yaml).
+This SDK is generated from our officially maintained [OpenAPI spec](https://github.com/hellosign/hellosign-openapi/blob/main/openapi.yaml).
 We've made important updates that introduce new functionality and create feature parity between the Dropbox Sign API and the SDK.
 However, some of these changes are considered "breaking" in the sense that they'll require you to update your existing code in order to continue using the SDK.
 Please refer to this [migration guide](https://developers.hellosign.com/docs/sdks/ruby/migration-guide/) for more information.
@@ -25,14 +25,14 @@ 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.0.0-beta2301
+- Package version: 1.0.1
 - Build package: org.openapitools.codegen.languages.RubyClientCodegen
 
 ## Installation
 
 ### Install gem
 ```shell
-gem install dropbox-sign --pre
+gem install dropbox-sign
 ```
 
 ### Build a gem
@@ -43,19 +43,17 @@ To build the Ruby code into a gem:
 gem build dropbox-sign.gemspec
 ```
 
-Then either install the gem locally:
+Then install the gem locally:
 
 ```shell
-gem install ./dropbox-sign-1.0.0-beta2301.gem
+gem install ./dropbox-sign-1.0.1.gem
 ```
 
-(for development, run `gem install --dev ./dropbox-sign-1.0.0-beta2301.gem` to install the development dependencies)
-
-or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
+(for development, run `gem install --dev ./dropbox-sign-1.0.1.gem` to install the development dependencies)
 
 Finally add this to the Gemfile:
 
-    gem 'dropbox-sign', '~> 1.0.0-beta2301'
+    gem 'dropbox-sign', '~> 1.0.1'
 
 ### Install from Git
 

data/VERSION

@@ -0,0 +1 @@
+1.0.1

data/bin/check-clean-git-status

@@ -0,0 +1,15 @@
+#!/usr/bin/env bash
+
+if [[ $(git status --porcelain) != '' ]]; then
+  printf "Working directory is dirty.\n";
+  printf "Please check that you committed any changes after running.\n"
+  printf "You may need to rebuild the SDK by running:\n";
+  printf "\t./run-build\n"
+
+  git status
+
+  exit 1
+else
+  echo "Working directory is clean!"
+  exit 0
+fi

data/bin/release

@@ -0,0 +1,39 @@
+#!/bin/sh
+
+set -e
+
+DIR=$(cd `dirname $0` && pwd)
+ROOT_DIR="${DIR}/.."
+
+PACKAGE_VERSION=$(cat "${ROOT_DIR}/VERSION")
+
+echo "Building for release ${PACKAGE_VERSION}"
+echo "---"
+
+echo "Setting up gem credentials..."
+set +x
+mkdir -p ~/.gem
+
+cat << EOF > ~/.gem/credentials
+---
+:rubygems_api_key: ${RUBYGEMS_API_KEY}
+EOF
+
+chmod 0600 ~/.gem/credentials
+set -x
+
+cd "${ROOT_DIR}"
+
+echo "Installing dependencies..."
+gem install bundler > /dev/null
+bundle install > /dev/null
+
+echo "Building..."
+rm -rf pkg
+rake build
+
+echo "Pushing release"
+gem push \
+  --config-file=~/.gem/credentials \
+  --key=rubygems \
+  ./pkg/dropbox-sign-${PACKAGE_VERSION}.gem

data/bin/ruby

@@ -9,6 +9,7 @@ WORKING_DIR="/app/ruby"
 docker run --rm \
   -e GEM_HOME="/.gem-cache" \
   -e BUNDLE_PATH="/.bundle-cache" \
+  -e RUBYGEMS_API_KEY=${RUBYGEMS_API_KEY-:''} \
   -v "${ROOT_DIR}:${WORKING_DIR}" \
   -v "dropbox-sign-sdk-gem-cache:/.gem-cache" \
   -v "dropbox-sign-sdk-bundle-cache:/.bundle-cache" \

data/docs/SignatureRequestApi.md

@@ -361,7 +361,7 @@ 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 = ["lawyer@dropboxsign.com", "lawyer@dropboxsign.com"]
+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
@@ -1138,8 +1138,8 @@ 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 = [
-  "lawyer@dropboxsign.com",
-  "lawyer@dropboxsign.com",
+  "lawyer1@dropboxsign.com",
+  "lawyer2@dropboxsign.com",
 ]
 data.files = [File.new("example_signature_request.pdf", "r")]
 data.metadata = {

data/docs/SignatureRequestCreateEmbeddedRequest.md

@@ -19,7 +19,7 @@
 | `field_options` | [```SubFieldOptions```](SubFieldOptions.md) |    |  |
 | `form_field_groups` | [```Array<SubFormFieldGroup>```](SubFormFieldGroup.md) |  Group information for fields defined in `form_fields_per_document`. String-indexed JSON array with `group_label` and `requirement` keys. `form_fields_per_document` must contain fields referencing a group defined in `form_field_groups`.  |  |
 | `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. (We&#39;re currently fixing a bug where this property only accepts a two-dimensional array. You can read about it here: &lt;a href&#x3D;&quot;/docs/openapi/form-fields-per-document&quot; target&#x3D;&quot;_blank&quot;&gt;Using Form Fields per Document&lt;/a&gt;.)<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`  |  |
+| `form_fields_per_document` | [```Array<SubFormFieldsPerDocumentBase>```](SubFormFieldsPerDocumentBase.md) |  The fields that should appear on the document, expressed as an array of objects. (We&#39;re currently fixing a bug where this property only accepts a two-dimensional array. 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] |
 | `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.  |  |

data/docs/SignatureRequestSendRequest.md

@@ -19,7 +19,7 @@
 | `field_options` | [```SubFieldOptions```](SubFieldOptions.md) |    |  |
 | `form_field_groups` | [```Array<SubFormFieldGroup>```](SubFormFieldGroup.md) |  Group information for fields defined in `form_fields_per_document`. String-indexed JSON array with `group_label` and `requirement` keys. `form_fields_per_document` must contain fields referencing a group defined in `form_field_groups`.  |  |
 | `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. (We&#39;re currently fixing a bug where this property only accepts a two-dimensional array. You can read about it here: &lt;a href&#x3D;&quot;/docs/openapi/form-fields-per-document&quot; target&#x3D;&quot;_blank&quot;&gt;Using Form Fields per Document&lt;/a&gt;.)<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`  |  |
+| `form_fields_per_document` | [```Array<SubFormFieldsPerDocumentBase>```](SubFormFieldsPerDocumentBase.md) |  The fields that should appear on the document, expressed as an array of objects. (We&#39;re currently fixing a bug where this property only accepts a two-dimensional array. 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] |
 | `message` | ```String``` |  The custom message in the email that will be sent to the signers.  |  |

data/docs/SubFormFieldsPerDocumentBase.md

@@ -1,6 +1,6 @@
 # Dropbox::Sign::SubFormFieldsPerDocumentBase
 
-The fields that should appear on the document, expressed as an array of objects. (We're currently fixing a bug where this property only accepts a two-dimensional array. You can read about it here: <a href="/docs/openapi/form-fields-per-document" target="_blank">Using Form Fields per Document</a>.)
+The fields that should appear on the document, expressed as an array of objects. (We're currently fixing a bug where this property only accepts a two-dimensional array. You can read about it here: [Using Form Fields per Document](/docs/openapi/form-fields-per-document).)
 
 **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.
 

data/docs/TemplateCreateEmbeddedDraftRequest.md

@@ -19,7 +19,7 @@
 | `force_subject_message` | ```Boolean``` |  Provide users the ability to review/edit the template subject and message.  |  [default to false] |
 | `form_field_groups` | [```Array<SubFormFieldGroup>```](SubFormFieldGroup.md) |  Group information for fields defined in `form_fields_per_document`. String-indexed JSON array with `group_label` and `requirement` keys. `form_fields_per_document` must contain fields referencing a group defined in `form_field_groups`.  |  |
 | `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. (We&#39;re currently fixing a bug where this property only accepts a two-dimensional array. You can read about it here: &lt;a href&#x3D;&quot;/docs/openapi/form-fields-per-document&quot; target&#x3D;&quot;_blank&quot;&gt;Using Form Fields per Document&lt;/a&gt;.)<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`  |  |
+| `form_fields_per_document` | [```Array<SubFormFieldsPerDocumentBase>```](SubFormFieldsPerDocumentBase.md) |  The fields that should appear on the document, expressed as an array of objects. (We&#39;re currently fixing a bug where this property only accepts a two-dimensional array. 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`  |  |
 | `merge_fields` | [```Array<SubMergeField>```](SubMergeField.md) |  Add merge fields to the template. Merge fields are placed by the user creating the template and used to pre-fill data by passing values into signature requests with the `custom_fields` parameter. If the signature request using that template *does not* pass a value into a merge field, then an empty field remains in the document.  |  |
 | `message` | ```String``` |  The default template email message.  |  |
 | `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.  |  |

data/docs/UnclaimedDraftApi.md

@@ -59,8 +59,8 @@ data.type = "request_signature"
 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 = [
-  "lawyer@dropboxsign.com",
-  "lawyer@dropboxsign.com",
+  "lawyer1@dropboxsign.com",
+  "lawyer2@dropboxsign.com",
 ]
 data.files = [File.new("example_signature_request.pdf", "r")]
 data.metadata = {

data/docs/UnclaimedDraftCreateEmbeddedRequest.md

@@ -22,7 +22,7 @@
 | `force_subject_message` | ```Boolean``` |  Provide users the ability to review/edit the subject and message.  |  [default to false] |
 | `form_field_groups` | [```Array<SubFormFieldGroup>```](SubFormFieldGroup.md) |  Group information for fields defined in `form_fields_per_document`. String-indexed JSON array with `group_label` and `requirement` keys. `form_fields_per_document` must contain fields referencing a group defined in `form_field_groups`.  |  |
 | `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. (We&#39;re currently fixing a bug where this property only accepts a two-dimensional array. You can read about it here: &lt;a href&#x3D;&quot;/docs/openapi/form-fields-per-document&quot; target&#x3D;&quot;_blank&quot;&gt;Using Form Fields per Document&lt;/a&gt;.)<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`  |  |
+| `form_fields_per_document` | [```Array<SubFormFieldsPerDocumentBase>```](SubFormFieldsPerDocumentBase.md) |  The fields that should appear on the document, expressed as an array of objects. (We&#39;re currently fixing a bug where this property only accepts a two-dimensional array. 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``` |  Send with a value of `true` if you wish to enable automatic Text Tag removal. Defaults to `false`. When using Text Tags it is preferred that you set this to `false` and hide your tags with white text or something similar because the automatic removal system can cause unwanted clipping. See the [Text Tags](https://app.hellosign.com/api/textTagsWalkthrough#TextTagIntro) walkthrough for more details.  |  [default to false] |
 | `hold_request` | ```Boolean``` |  The request from this draft will not automatically send to signers post-claim if set to `true`. Requester must [release](/api/reference/operation/signatureRequestReleaseHold/) the request from hold when ready to send. Defaults to `false`.  |  [default to false] |
 | `is_for_embedded_signing` | ```Boolean``` |  The request created from this draft will also be signable in embedded mode if set to `true`. Defaults to `false`.  |  [default to false] |

data/docs/UnclaimedDraftCreateRequest.md

@@ -17,7 +17,7 @@
 | `field_options` | [```SubFieldOptions```](SubFieldOptions.md) |    |  |
 | `form_field_groups` | [```Array<SubFormFieldGroup>```](SubFormFieldGroup.md) |  Group information for fields defined in `form_fields_per_document`. String-indexed JSON array with `group_label` and `requirement` keys. `form_fields_per_document` must contain fields referencing a group defined in `form_field_groups`.  |  |
 | `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. (We&#39;re currently fixing a bug where this property only accepts a two-dimensional array. You can read about it here: &lt;a href&#x3D;&quot;/docs/openapi/form-fields-per-document&quot; target&#x3D;&quot;_blank&quot;&gt;Using Form Fields per Document&lt;/a&gt;.)<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`  |  |
+| `form_fields_per_document` | [```Array<SubFormFieldsPerDocumentBase>```](SubFormFieldsPerDocumentBase.md) |  The fields that should appear on the document, expressed as an array of objects. (We&#39;re currently fixing a bug where this property only accepts a two-dimensional array. 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``` |  Send with a value of `true` if you wish to enable automatic Text Tag removal. Defaults to `false`. When using Text Tags it is preferred that you set this to `false` and hide your tags with white text or something similar because the automatic removal system can cause unwanted clipping. See the [Text Tags](https://app.hellosign.com/api/textTagsWalkthrough#TextTagIntro) walkthrough for more details.  |  [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.  |  |

data/examples/EventCallback.rb

@@ -18,10 +18,7 @@ callback_data = {
   },
 }
 
-callback_event = Dropbox::Sign::ApiClient.new.convert_to_type(
-  callback_data,
-  "Dropbox::Sign::EventCallbackRequest"
-) || Dropbox::Sign::EventCallbackRequest.new
+callback_event = Dropbox::Sign::EventCallbackRequest.init(callback_data)
 
 # verify that a callback came from HelloSign.com
 if Dropbox::Sign::EventCallbackHelper.is_valid(api_key, callback_event)

data/examples/SignatureRequestCreateEmbedded.rb

@@ -33,7 +33,7 @@ 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 = ["lawyer@dropboxsign.com", "lawyer@dropboxsign.com"]
+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

data/examples/SignatureRequestSend.rb

@@ -36,8 +36,8 @@ 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 = [
-  "lawyer@dropboxsign.com",
-  "lawyer@dropboxsign.com",
+  "lawyer1@dropboxsign.com",
+  "lawyer2@dropboxsign.com",
 ]
 data.files = [File.new("example_signature_request.pdf", "r")]
 data.metadata = {

data/examples/UnclaimedDraftCreate.rb

@@ -36,8 +36,8 @@ data.type = "request_signature"
 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 = [
-  "lawyer@dropboxsign.com",
-  "lawyer@dropboxsign.com",
+  "lawyer1@dropboxsign.com",
+  "lawyer2@dropboxsign.com",
 ]
 data.files = [File.new("example_signature_request.pdf", "r")]
 data.metadata = {

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

@@ -19,15 +19,19 @@ end
 module Dropbox::Sign
   class AccountCreateRequest
     # The email address which will be associated with the new Account.
+    # @return [String]
     attr_accessor :email_address
 
     # Used when creating a new account with OAuth authorization.  See [OAuth 2.0 Authorization](https://app.hellosign.com/api/oauthWalkthrough#OAuthAuthorization)
+    # @return [String]
     attr_accessor :client_id
 
     # Used when creating a new account with OAuth authorization.  See [OAuth 2.0 Authorization](https://app.hellosign.com/api/oauthWalkthrough#OAuthAuthorization)
+    # @return [String]
     attr_accessor :client_secret
 
     # 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.
+    # @return [String]
     attr_accessor :locale
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -18,11 +18,14 @@ end
 
 module Dropbox::Sign
   class AccountCreateResponse
+    # @return [AccountResponse]
     attr_accessor :account
 
+    # @return [OAuthTokenResponse]
     attr_accessor :oauth_data
 
     # A list of warnings.
+    # @return [Array<WarningResponse>]
     attr_accessor :warnings
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -18,9 +18,11 @@ end
 
 module Dropbox::Sign
   class AccountGetResponse
+    # @return [AccountResponse]
     attr_accessor :account
 
     # A list of warnings.
+    # @return [Array<WarningResponse>]
     attr_accessor :warnings
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -19,32 +19,42 @@ end
 module Dropbox::Sign
   class AccountResponse
     # The ID of the Account
+    # @return [String]
     attr_accessor :account_id
 
     # The email address associated with the Account.
+    # @return [String]
     attr_accessor :email_address
 
     # Returns `true` if the user has been locked out of their account by a team admin.
+    # @return [Boolean]
     attr_accessor :is_locked
 
     # Returns `true` if the user has a paid Dropbox Sign account.
+    # @return [Boolean]
     attr_accessor :is_paid_hs
 
     # Returns `true` if the user has a paid HelloFax account.
+    # @return [Boolean]
     attr_accessor :is_paid_hf
 
+    # @return [AccountResponseQuotas]
     attr_accessor :quotas
 
     # The URL that Dropbox Sign events will `POST` to.
+    # @return [String, nil]
     attr_accessor :callback_url
 
     # The membership role for the team.
+    # @return [String, nil]
     attr_accessor :role_code
 
     # The id of the team account belongs to.
+    # @return [String, nil]
     attr_accessor :team_id
 
     # 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.
+    # @return [String, nil]
     attr_accessor :locale
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -20,18 +20,23 @@ module Dropbox::Sign
   # Details concerning remaining monthly quotas.
   class AccountResponseQuotas
     # API signature requests remaining.
+    # @return [Integer, nil]
     attr_accessor :api_signature_requests_left
 
     # Signature requests remaining.
+    # @return [Integer, nil]
     attr_accessor :documents_left
 
     # Total API templates allowed.
+    # @return [Integer, nil]
     attr_accessor :templates_total
 
     # API templates remaining.
+    # @return [Integer, nil]
     attr_accessor :templates_left
 
     # SMS verifications  remaining.
+    # @return [Integer, nil]
     attr_accessor :sms_verifications_left
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -19,12 +19,15 @@ end
 module Dropbox::Sign
   class AccountUpdateRequest
     # The ID of the Account
+    # @return [String, nil]
     attr_accessor :account_id
 
     # The URL that Dropbox Sign should POST events to.
+    # @return [String]
     attr_accessor :callback_url
 
     # 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.
+    # @return [String]
     attr_accessor :locale
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -19,6 +19,7 @@ end
 module Dropbox::Sign
   class AccountVerifyRequest
     # Email address to run the verification for.
+    # @return [String]
     attr_accessor :email_address
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -18,9 +18,11 @@ end
 
 module Dropbox::Sign
   class AccountVerifyResponse
+    # @return [AccountVerifyResponseAccount]
     attr_accessor :account
 
     # A list of warnings.
+    # @return [Array<WarningResponse>]
     attr_accessor :warnings
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -19,6 +19,7 @@ end
 module Dropbox::Sign
   class AccountVerifyResponseAccount
     # The email address associated with the Account.
+    # @return [String]
     attr_accessor :email_address
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -19,21 +19,28 @@ end
 module Dropbox::Sign
   class ApiAppCreateRequest
     # The domain names the ApiApp will be associated with.
+    # @return [Array<String>]
     attr_accessor :domains
 
     # The name you want to assign to the ApiApp.
+    # @return [String]
     attr_accessor :name
 
     # The URL at which the ApiApp should receive event callbacks.
+    # @return [String]
     attr_accessor :callback_url
 
     # An image file to use as a custom logo in embedded contexts. (Only applies to some API plans)
+    # @return [File]
     attr_accessor :custom_logo_file
 
+    # @return [SubOAuth]
     attr_accessor :oauth
 
+    # @return [SubOptions]
     attr_accessor :options
 
+    # @return [SubWhiteLabelingOptions]
     attr_accessor :white_labeling_options
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -18,9 +18,11 @@ end
 
 module Dropbox::Sign
   class ApiAppGetResponse
+    # @return [ApiAppResponse]
     attr_accessor :api_app
 
     # A list of warnings.
+    # @return [Array<WarningResponse>]
     attr_accessor :warnings
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -19,11 +19,14 @@ end
 module Dropbox::Sign
   class ApiAppListResponse
     # Contains information about API Apps.
+    # @return [Array<ApiAppResponse>]
     attr_accessor :api_apps
 
+    # @return [ListInfoResponse]
     attr_accessor :list_info
 
     # A list of warnings.
+    # @return [Array<WarningResponse>]
     attr_accessor :warnings
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -20,29 +20,39 @@ module Dropbox::Sign
   # Contains information about an API App.
   class ApiAppResponse
     # The app's callback URL (for events)
+    # @return [String, nil]
     attr_accessor :callback_url
 
     # The app's client id
+    # @return [String]
     attr_accessor :client_id
 
     # The time that the app was created
+    # @return [Integer]
     attr_accessor :created_at
 
     # The domain name(s) associated with the app
+    # @return [Array<String>]
     attr_accessor :domains
 
     # The name of the app
+    # @return [String]
     attr_accessor :name
 
     # Boolean to indicate if the app has been approved
+    # @return [Boolean]
     attr_accessor :is_approved
 
+    # @return [ApiAppResponseOAuth, nil]
     attr_accessor :oauth
 
+    # @return [ApiAppResponseOptions, nil]
     attr_accessor :options
 
+    # @return [ApiAppResponseOwnerAccount]
     attr_accessor :owner_account
 
+    # @return [ApiAppResponseWhiteLabelingOptions, nil]
     attr_accessor :white_labeling_options
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -20,15 +20,19 @@ module Dropbox::Sign
   # An object describing the app's OAuth properties, or null if OAuth is not configured for the app.
   class ApiAppResponseOAuth
     # The app's OAuth callback URL.
+    # @return [String]
     attr_accessor :callback_url
 
     # The app's OAuth secret, or null if the app does not belong to user.
+    # @return [String]
     attr_accessor :secret
 
     # Array of OAuth scopes used by the app.
+    # @return [Array<String>]
     attr_accessor :scopes
 
     # Boolean indicating whether the app owner or the account granting permission is billed for OAuth requests.
+    # @return [Boolean]
     attr_accessor :charges_users
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -20,6 +20,7 @@ module Dropbox::Sign
   # An object with options that override account settings.
   class ApiAppResponseOptions
     # Boolean denoting if signers can \"Insert Everywhere\" in one click while signing a document
+    # @return [Boolean]
     attr_accessor :can_insert_everywhere
 
     # Attribute mapping from ruby-style variable name to JSON key.

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

@@ -20,9 +20,11 @@ module Dropbox::Sign
   # An object describing the app's owner
   class ApiAppResponseOwnerAccount
     # The owner account's ID
+    # @return [String]
     attr_accessor :account_id
 
     # The owner account's email address
+    # @return [String]
     attr_accessor :email_address
 
     # Attribute mapping from ruby-style variable name to JSON key.