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 integrates with the Zendry API to manage Pix receipts, specifically allowing users to list QR codes associated with Pix transactions. It supports fetching QR codes with optional filters, enabling users to retrieve and manage Pix payment QR codes efficiently. This is useful for financial applications, payment tracking, and automated payment processing workflows.

Use Case Examples

  1. List all Pix QR codes with optional filtering parameters such as generator name, document, or expiration time.
  2. Retrieve QR codes for Pix payments to monitor or 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.
Additional Fields Optional parameters to refine 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 as per API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the list of Pix QR codes and related data.

Dependencies

  • Zendry API access requiring a valid Bearer access token.

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to access Pix QR code data.
  • Verify that the JSON provided in 'Required Fields' and 'Filters' is valid and correctly formatted to avoid parsing errors.
  • Check that mandatory parameters like 'end_to_end' or 'reference_id' are provided when required by specific operations.
  • Common error messages include invalid token errors, missing required parameters, and JSON parsing errors. Resolving these involves validating credentials, providing all required inputs, and ensuring JSON syntax correctness.

Links

Discussion