Zendry Global API 1.0 icon

Zendry Global API 1.0

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

Actions120

Overview

This node integrates with the Zendry API to perform various operations related to the Checkout resource, specifically listing QR Codes in this context. It allows users to retrieve a list of QR Codes generated for Pix payments, which can be filtered and customized using optional parameters. This is useful for businesses or developers who need to manage and track QR Code-based payment requests programmatically.

Use Case Examples

  1. A business uses this node to fetch all active QR Codes for Pix payments to display them in their internal dashboard.
  2. A developer integrates this node to filter QR Codes by generator name or expiration time to monitor payment requests.
  3. An e-commerce platform uses this node to list QR Codes with specific external references for reconciliation purposes.

Properties

Name Meaning
Access Token A valid Bearer access token for authenticating with the Zendry API.
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 filter or customize the QR Code listing, such as generator name, document, external reference, expiration time, external link, JSON filters, webhook settings, and authorization headers.
Required Fields (JSON) JSON object containing required fields for the operation, if any, according to the API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the list of QR Codes and their details.

Dependencies

  • Requires a valid Bearer access token for Zendry API authentication.

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to access the Checkout resource.
  • Verify that the JSON provided in 'Required Fields (JSON)' and 'Filters (JSON)' is valid and correctly formatted to avoid parsing errors.
  • If the operation requires specific parameters (e.g., filters), ensure they are provided; otherwise, the API may return errors or empty results.
  • Check the Base URL if the API endpoint is unreachable or returns errors, especially if using a custom URL.

Links

Discussion