You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: api/templateApi.ts
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -290,7 +290,7 @@ export class TemplateApi {
290
290
});
291
291
}
292
292
/**
293
-
* Creates a template that can then be used.
293
+
* 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.
@@ -20079,7 +20119,7 @@ var SignatureRequestEditRequest = class _SignatureRequestEditRequest {
20079
20119
*/
20080
20120
this["hideTextTags"] = false;
20081
20121
/**
20082
-
* 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.
20122
+
* 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.
20083
20123
*/
20084
20124
this["isEid"] = false;
20085
20125
/**
@@ -20240,7 +20280,7 @@ var SignatureRequestEditWithTemplateRequest = class _SignatureRequestEditWithTem
20240
20280
*/
20241
20281
this["allowDecline"] = false;
20242
20282
/**
20243
-
* 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.
20283
+
* 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.
20244
20284
*/
20245
20285
this["isEid"] = false;
20246
20286
/**
@@ -21346,7 +21386,7 @@ var SignatureRequestSendRequest = class _SignatureRequestSendRequest {
21346
21386
*/
21347
21387
this["isQualifiedSignature"] = false;
21348
21388
/**
21349
-
* 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.
21389
+
* 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.
21350
21390
*/
21351
21391
this["isEid"] = false;
21352
21392
/**
@@ -21518,7 +21558,7 @@ var SignatureRequestSendWithTemplateRequest = class _SignatureRequestSendWithTem
21518
21558
*/
21519
21559
this["isQualifiedSignature"] = false;
21520
21560
/**
21521
-
* 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.
21561
+
* 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.
21522
21562
*/
21523
21563
this["isEid"] = false;
21524
21564
/**
@@ -23090,6 +23130,10 @@ var SubSigningOptions = class _SubSigningOptions {
23090
23130
* Allows uploading the signature
23091
23131
*/
23092
23132
this["upload"] = false;
23133
+
/**
23134
+
* Turning on advanced signature details for the signature request
23135
+
*/
23136
+
this["forceAdvancedSignatureDetails"] = false;
23093
23137
}
23094
23138
static {
23095
23139
this.discriminator = void 0;
@@ -23120,6 +23164,11 @@ var SubSigningOptions = class _SubSigningOptions {
23120
23164
name: "upload",
23121
23165
baseName: "upload",
23122
23166
type: "boolean"
23167
+
},
23168
+
{
23169
+
name: "forceAdvancedSignatureDetails",
23170
+
baseName: "force_advanced_signature_details",
23171
+
type: "boolean"
23123
23172
}
23124
23173
];
23125
23174
}
@@ -24336,29 +24385,6 @@ var TemplateCreateResponseTemplate = class _TemplateCreateResponseTemplate {
24336
24385
}
24337
24386
};
24338
24387
24339
-
// model/templateEditResponse.ts
24340
-
var TemplateEditResponse = class _TemplateEditResponse {
24341
-
static {
24342
-
this.discriminator = void 0;
24343
-
}
24344
-
static {
24345
-
this.attributeTypeMap = [
24346
-
{
24347
-
name: "templateId",
24348
-
baseName: "template_id",
24349
-
type: "string"
24350
-
}
24351
-
];
24352
-
}
24353
-
static getAttributeTypeMap() {
24354
-
return _TemplateEditResponse.attributeTypeMap;
24355
-
}
24356
-
/** Attempt to instantiate and hydrate a new instance of this class */
var TemplateGetResponse = class _TemplateGetResponse {
24364
24390
static {
@@ -26803,6 +26829,7 @@ var typeMap = {
26803
26829
AccountGetResponse,
26804
26830
AccountResponse,
26805
26831
AccountResponseQuotas,
26832
+
AccountResponseSettings,
26806
26833
AccountResponseUsage,
26807
26834
AccountUpdateRequest,
26808
26835
AccountVerifyRequest,
@@ -26939,7 +26966,6 @@ var typeMap = {
26939
26966
TemplateCreateRequest,
26940
26967
TemplateCreateResponse,
26941
26968
TemplateCreateResponseTemplate,
26942
-
TemplateEditResponse,
26943
26969
TemplateGetResponse,
26944
26970
TemplateListResponse,
26945
26971
TemplateRemoveUserRequest,
@@ -34474,7 +34500,7 @@ var TemplateApi = class {
34474
34500
});
34475
34501
}
34476
34502
/**
34477
-
* Creates a template that can then be used.
34503
+
* 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.
34478
34504
* @summary Create Template
34479
34505
* @param templateCreateRequest
34480
34506
* @param options
@@ -36235,7 +36261,7 @@ var HttpError = class extends Error {
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.
Copy file name to clipboardExpand all lines: docs/model/AccountResponse.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,5 +17,6 @@ Name | Type | Description | Notes
17
17
|`teamId`|```string```| The id of the team account belongs to. ||
18
18
|`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. ||
|`signerAccessCodes`|```boolean```| Returns `true` if _Custom access codes_ is enabled in Admin Console. [Read more](https://developers.hellosign.com/docs/sms-tools/walkthrough). ||
10
+
|`smsDelivery`|```boolean```| Returns `true` if _Text message_ is enabled in Admin Console. [Read more](https://developers.hellosign.com/docs/sms-tools/walkthrough). ||
11
+
|`smsAuthentication`|```boolean```| Returns `true` if _Signer authentication_ is enabled in Admin Console. [Read more](https://developers.hellosign.com/docs/sms-tools/walkthrough). ||
12
+
13
+
[[Back to Model list]](../../README.md#models)[[Back to API list]](../../README.md#endpoints)[[Back to README]](../../README.md)
Copy file name to clipboardExpand all lines: docs/model/SignatureRequestEditRequest.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ Name | Type | Description | Notes
21
21
|`formFieldRules`|[```Array<SubFormFieldRule>```](SubFormFieldRule.md)| Conditional Logic rules for fields defined in `form_fields_per_document`. ||
22
22
| `formFieldsPerDocument` | [```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` | |
23
23
|`hideTextTags`|```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]|
24
-
|`isEid`|```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.<br><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]|
24
+
|`isEid`|```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.<br><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]|
25
25
|`message`|```string```| The custom message in the email that will be sent to the signers. ||
26
26
|`metadata`|```{ [key: string]: any; }```| 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'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. ||
0 commit comments