Autentique icon

Autentique

Trabalhe com dados da API do Autentique para assinaturas digitais

Actions22

Document → Create

AI-generated

Overview

This node operation creates a new document for digital signature using the Autentique API. It allows users to upload a document file in Base64 format, specify the document name, and define an array of signatories with their details and actions. Additional options include setting reminders, footer position, qualified signature, scrolling requirement, and other signature-related settings. The node prepares a multipart/form-data request with the document metadata and file content, then sends it to the Autentique API to create the document and initiate the signing process.

Use Case Examples

  1. Creating a contract document with multiple signatories for electronic signature.
  2. Uploading a PDF document and specifying signature order and reminders for signatories.
  3. Creating a document with qualified digital signatures and custom audit page settings.

Properties

Name Meaning
Document Name The name of the document to be created.
File Content (Base64) The content of the document file encoded in Base64 format. Accepted formats include PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX, ODT, ODS, ODP, RTF, HTML, TXT. Maximum size is 20MB.
Signatures A JSON array of signatories, each with name, email, and action (SIGN, APPROVE, SIGN_AS_A_WITNESS, RECOGNIZE).
Refusable Whether the document can be refused by signatories.
Sortable Whether signatures must follow a specific order.
Message Custom message sent to the emails of the signatories.
Reminder Frequency of automatic reminders sent to signatories.
Footer Position Position of the footer in the document.
Qualified Signature Whether to enable qualified signature using digital certificates.
Scrolling Required Whether the signatory must scroll through the entire page before signing.
Stop on Rejected Whether to stop other signatories from signing if the document is refused.
New Signature Style Whether to enable new signature fields style.
Show Audit Page Whether to show the audit page at the end of the document.
Ignore CPF Whether to remove the requirement to fill in CPF to sign.
Ignore Birthdate Whether to remove the requirement to fill in birthdate.
Deadline Deadline date for signatures in ISO format.
Organization ID ID of the organization where the document will be created (optional).
Folder ID ID of the folder where the document will be created (optional).

Output

JSON

  • id - The unique identifier of the created document.
  • name - The name of the created document.
  • refusable - Indicates if the document can be refused.
  • sortable - Indicates if the signatures must follow a specific order.
  • created_at - Timestamp when the document was created.
  • signatures
    • public_id - Public identifier of each signature.
    • name - Name of the signatory.
    • email - Email of the signatory.
    • action
      * name - Action the signatory must perform (e.g., SIGN).
    • link
      * short_link - Short link URL for the signature.

Dependencies

  • Autentique API
  • An API key credential for authentication

Troubleshooting

  • Ensure the File Content is a valid Base64 string; invalid Base64 will cause errors.
  • Signatures must be a valid non-empty JSON array; invalid JSON or empty array will cause errors.
  • File size must not exceed 20MB; large files may cause request failures.
  • Check that required parameters like Document Name and Signatures are provided.
  • If the API returns errors, verify the API key credential and network connectivity.

Links

Discussion