Zendry Global API 1.0 icon

Zendry Global API 1.0

Acesso universal à API Zendry (Pix, Payments, Webhooks, Account, Crypto, Checkout) via AccessToken

Actions120

Crypto → List QRCodes

AI-generated

Overview

This node provides access to the Zendry API, specifically supporting various operations across multiple resources such as Pix receipts, payments, webhooks, account info, crypto transactions, and checkout processes. For the 'Crypto' resource with the 'List QRCodes' operation, it allows users to retrieve a list of QR codes related to crypto payments or transactions. This is useful for scenarios where users need to manage or monitor QR codes generated for crypto payments, enabling integration with the Zendry platform for automated workflows.

Use Case Examples

  1. A user wants to list all QR codes generated for crypto payments to reconcile transactions.
  2. A business integrates this node to fetch QR codes for crypto payments to display or process them further in their system.

Properties

Name Meaning
Access Token A valid Bearer access token for authenticating API requests to Zendry.
Base URL The base URL of the Zendry API, defaulting to https://api.zendry.com.br, which should not be changed unless necessary.
Additional Fields Optional parameters to refine or customize the API request, such as generator name, document, external reference, expiration time, external link, filters in JSON format, webhook URL and type, authorization header for webhook, and payment authorization status.
Required Fields (JSON) JSON object containing required fields for the operation as per API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the list of QR codes or relevant data for the requested operation.

Dependencies

  • Requires a valid Zendry API access token for authentication.

Troubleshooting

  • Common issues include invalid or expired access tokens leading to authentication errors.
  • Malformed JSON in the 'Required Fields (JSON)' or 'Filters (JSON)' properties can cause parsing errors; ensure valid JSON format.
  • Missing required parameters such as 'end_to_end' or 'reference_id' for specific operations will result in errors; verify all mandatory fields are provided.

Links

Discussion