Autentique icon

Autentique

Trabalhe com dados da API do Autentique para assinaturas digitais

Actions19

Overview

The "Get Many" operation of the Document resource in this node allows users to retrieve multiple documents from the Autentique digital signature platform. This operation supports pagination and limits on the number of results returned, making it useful for workflows that need to list or process batches of documents.

Common scenarios where this node is beneficial include:

  • Fetching a list of recent documents for reporting or auditing.
  • Integrating document data into other systems or dashboards.
  • Automating batch processing or monitoring of documents awaiting signatures.

For example, you could use this node to get the first 50 documents created in your account and then loop through them to check their status or extract signature information.

Properties

Name Meaning
Limit Max number of results to return. Users can specify how many documents to fetch per call.
Page Page number of the results to retrieve, starting at 1. Enables pagination through results.

Output

The output JSON contains a structure with the following fields:

  • data: An array of document objects, each including:

    • id: Unique identifier of the document.
    • name: Name/title of the document.
    • refusable: Boolean indicating if the document can be refused.
    • sortable: Boolean indicating if signatures must follow a specific order.
    • created_at: Timestamp when the document was created.
    • signatures: Array of signature objects associated with the document, each containing:
      • public_id: Public ID of the signature.
      • name: Name of the signer.
      • email: Email of the signer.
      • created_at: When the signature was created.
      • action: Object with the name of the action (e.g., sign, approve).

  • Pagination metadata:

    • total: Total number of documents available.
    • per_page: Number of documents per page.
    • current_page: Current page number.
    • last_page: Last available page number.

This structured output enables easy iteration over documents and access to their signature details.

Dependencies

  • Requires an API key credential for authenticating with the Autentique API.
  • The node makes HTTP POST requests to the Autentique GraphQL endpoint (https://api.autentique.com.br/v2/graphql).
  • No additional external dependencies are required beyond the configured API authentication.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Requesting a page number beyond the last page will return empty data arrays.
    • Setting the limit too high may result in slower responses or API rate limiting.

  • Error messages:

    • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
    • GraphQL errors may occur if parameters are malformed; ensure limit and page are positive integers.
    • Network errors suggest connectivity issues; check internet connection and API availability.

Links and References

Discussion