Zendry Global API 1.0 icon

Zendry Global API 1.0

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

Actions120

Payments (Pix Out) → List QRCodes

AI-generated

Overview

This node interacts with the Zendry API to manage Pix Out payments, specifically allowing users to list QR codes related to payments. It supports various operations across multiple resources like receipts, payments, webhooks, account, crypto, and checkout, but here it focuses on the 'List QRCodes' operation under the 'Payments (Pix Out)' resource. This operation fetches a list of QR codes, optionally filtered by user-defined JSON filters. It is useful for scenarios where users need to retrieve and manage payment QR codes programmatically, such as in financial applications or payment processing workflows.

Use Case Examples

  1. A business automates the retrieval of all active Pix payment QR codes to display on their website.
  2. A financial service integrates this node to monitor and list QR codes generated for payments to reconcile transactions.

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 refine the request, including generator name, document, external reference, expiration time, external link, JSON filters for listing, 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 or relevant data for the requested operation.

Dependencies

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

Troubleshooting

  • Ensure the Access Token is valid and has not expired to avoid authentication errors.
  • Verify that the 'requestBody' JSON is correctly formatted; invalid JSON will cause errors.
  • Mandatory parameters like 'filters' (if used) must be valid JSON; otherwise, the node will throw an error.
  • If required parameters for the operation are missing (e.g., reference IDs), the node will throw an error indicating the missing field.

Links

Discussion