Source: schemas/sign-request-base.generated.ts

  1. import * as schemas from '.';
  2. /**
  3.  * Box Sign request (Base)
  4.  *
  5.  * A standard representation of a signature request object.
  6.  */
  7. export interface SignRequestBase {
  8. 	/**
  9. 	 * Indicates if the sender should receive a `prepare_url` in the response to complete document preparation using the UI.
  10. 	 * Example: true
  11. 	 */
  12. 	is_document_preparation_needed?: boolean;
  13. 	/**
  14. 	 * When specified, the signature request will be redirected to this url when a document is signed.
  15. 	 * Example: https://www.example.com
  16. 	 */
  17. 	redirect_url?: string;
  18. 	/**
  19. 	 * The uri that a signer will be redirected to after declining to sign a document.
  20. 	 * Example: https://declined-redirect.com
  21. 	 */
  22. 	declined_redirect_url?: string;
  23. 	/**
  24. 	 * Disables the usage of signatures generated by typing (text).
  25. 	 * Example: true
  26. 	 * @default true
  27. 	 */
  28. 	are_text_signatures_enabled?: boolean;
  29. 	/**
  30. 	 * Subject of sign request email. This is cleaned by sign request. If this field is not passed, a default subject will be used.
  31. 	 * Example: Sign Request from Acme
  32. 	 */
  33. 	email_subject?: string;
  34. 	/**
  35. 	 * Message to include in sign request email. The field is cleaned through sanitization of specific characters. However, some html tags are allowed. Links included in the message are also converted to hyperlinks in the email. The message may contain the following html tags including `a`, `abbr`, `acronym`, `b`, `blockquote`, `code`, `em`, `i`, `ul`, `li`, `ol`, and `strong`. Be aware that when the text to html ratio is too high, the email may end up in spam filters. Custom styles on these tags are not allowed. If this field is not passed, a default message will be used.
  36. 	 * Example: Hello! Please sign the document below
  37. 	 */
  38. 	email_message?: string;
  39. 	/**
  40. 	 * Reminds signers to sign a document on day 3, 8, 13 and 18. Reminders are only sent to outstanding signers.
  41. 	 * Example: true
  42. 	 */
  43. 	are_reminders_enabled?: boolean;
  44. 	/**
  45. 	 * Name of the signature request.
  46. 	 * Example: name
  47. 	 */
  48. 	name?: string;
  49. 	/**
  50. 	 * When a document contains sign-related tags in the content, you can prefill them using this `prefill_tags` by referencing the 'id' of the tag as the `external_id` field of the prefill tag.
  51. 	 */
  52. 	prefill_tags?: schemas.SignRequestPrefillTag[];
  53. 	/**
  54. 	 * Set the number of days after which the created signature request will automatically expire if not completed. By default, we do not apply any expiration date on signature requests, and the signature request does not expire.
  55. 	 * Example: 2
  56. 	 */
  57. 	days_valid?: number;
  58. 	/**
  59. 	 * This can be used to reference an ID in an external system that the sign request is related to.
  60. 	 * Example: 123
  61. 	 */
  62. 	external_id?: string;
  63. 	/**
  64. 	 * Forces signers to verify a text message prior to viewing the document. You must specify the phone number of signers to have this setting apply to them.
  65. 	 * Example: true
  66. 	 */
  67. 	is_phone_verification_required_to_view?: boolean;
  68. 	/**
  69. 	 * When a signature request is created from a template this field will indicate the id of that template.
  70. 	 * Example: 123075213-af2c8822-3ef2-4952-8557-52d69c2fe9cb
  71. 	 */
  72. 	template_id?: string;
  73. 	/**
  74. 	 * Used as an optional system name to appear in the signature log next to the signers who have been assigned the `embed_url_external_id`.
  75. 	 * Example: Box
  76. 	 */
  77. 	external_system_name?: string;
  78. }