Zendry Global API 1.0 icon

Zendry Global API 1.0

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

Actions120

Overview

This node interacts with the Zendry API to perform various operations related to accounts, including listing QR codes. Specifically, for the 'Account' resource and 'List QRCodes' operation, it fetches a list of QR codes associated with the account. This is useful for scenarios where you need to retrieve and manage QR codes generated for payments or other purposes within the Zendry platform. For example, a business could use this node to automate the retrieval of all active QR codes for tracking or reporting.

Use Case Examples

  1. Retrieve all QR codes generated for an account to display in a dashboard.
  2. Automate the monitoring of QR codes to check their status or expiration.

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 URL and type, authorization header for webhook, and payment authorization status.
Required Fields (JSON) JSON object containing required fields for the operation as per the API documentation.

Output

JSON

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

Dependencies

  • Zendry API access requiring a valid Bearer access token

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to access the account QR codes.
  • Verify that the Base URL is correct and reachable; the default should be used unless a custom endpoint is required.
  • If using filters in Additional Fields, ensure the JSON is valid to avoid parsing errors.
  • Common error messages include missing required parameters like access token or invalid JSON in requestBody; these should be corrected as per the error details.

Links

Discussion