- ERROR WHEN ENCODING PLATINUM NOTES HOW TO
- ERROR WHEN ENCODING PLATINUM NOTES PDF
- ERROR WHEN ENCODING PLATINUM NOTES CODE
Listen for the "signature_request_canceled" event. It is recommended that a callback handler be implemented to The cancelation isĬonfirmed via the "signature_request_canceled" event. This 200 OK response does not indicate a successful cancelation of the signature request itself. Is eligible to be canceled and has been successfully queued. Cancelation is asynchronousĪnd a successful call to this endpoint will return an empty 200 OK response if the signature request
ERROR WHEN ENCODING PLATINUM NOTES CODE
They will receive a HTTP 410 status code indicating that the resource has been deleted. If they try to access the signature request The request will be canceled and signers will no longer be able to sign.
custom_fields: an array of custom field values using the field name or API id as keys (optional) You may only specify field values here, any other options should be set in the custom_fields request parameter.Ĭancels an incomplete signature request. (optional) Note: Not available in test mode and requires a Platinum plan or higher. sms_phone_number: An E.164 formatted phone number that will receive a code via SMS to access this signer's signature page. pin: the 4- to 12-character access code that will secure this signer's signature page (optional). email_address: email address of the signer filling the role of RoleName. name: the name of the signer filling the role of RoleName. signers: an array of signers using the RoleName as keys (currently only one signer is supported per SignatureRequest). Each element in the array can have the following two items: Required unless a signer_file is used, you may not use both. Mary, gd9as5b, 123 LLC signer_list is a JSON array defining values and options for signer fields. The following is an example of form_field_rules along with the required form_fields_per_document, prior to serialization to a string for the API request: "type": "change-field-visibility" | "change-group-visibility" The required shape of form_field_rules is actions: for identifying the "do" part of "when x do y". triggers: for identifying the "when" part of " when x do y". trigger_operator: currently only AND is supported. The following is an example of form_field_groups along with the required form_fields_per_document, prior to serialization to a string for the API request:Ĭonditional Logic rules for fields defined in form_fields_per_document. The required shape of form_field_groups is String-indexed JSON array with group_label and requirement keys.įorm_fields_per_document must contain fields referencing a group defined in Group information for fields defined in form_fields_per_document. The following is an example of a form_fields_per_document for a 2-document request with a text field and signature field on the first page of the document, prior to serialization to a string for the API request: Check out the list of validation types to learn more about the possible values. This is a display name for the field.Įach text field may contain a validation_type parameter. Optionally, each field may contain a name (string) parameter. If your type is 'text-merge' you can set this to 'sender', so the field is non-editable by any signer. signer - (int | string) signer index identified by the offset %i% in the signers parameter, indicating which signer should fill out the field. required - (boolean) whether this field is requiredħ. width & height - (int) size of the field in pixelsĦ. ERROR WHEN ENCODING PLATINUM NOTES HOW TO
Check out the differences between both coordinate systems and how to use them.ĥ. When the page number parameter is supplied, the API will use the new coordinate system.ī.
ERROR WHEN ENCODING PLATINUM NOTES PDF
page - (int) page in the document where the field should be placed (requires documents be PDF files)Ī. x & y - (int) location coordinates of the field in pixelsĤ. api_id - (string) an identifier for the field that is unique across all documents in the requestģ. In the case of a file with no fields, an empty list must be specified.ġ. One document array is required for each file provided With each containing an array of form fields. The fields that should appear on the document,Įxpressed as a 2-dimensional JSON array serialized to a string.
0 kommentar(er)
