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 Out payments, specifically allowing users to list payments made via Pix. It is useful for financial operations where tracking and managing outgoing Pix payments is required. For example, a business can use this node to retrieve a list of all Pix payments they have made, filter them by various criteria, and process or analyze payment data within an automated workflow.

Use Case Examples

  1. A business wants to automate the reconciliation of Pix payments by listing all payments made in the last month and exporting the data to a spreadsheet.
  2. A financial service provider uses the node to monitor authorized Pix payments and trigger alerts for any unauthorized transactions.

Properties

Name Meaning
Access Token A valid Bearer access token for authenticating requests to 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 list payments 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 the API documentation.

Output

JSON

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

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.
  • The 'requestBody' must be a valid JSON string; invalid JSON will cause an error.
  • Required parameters such as 'reference_code' or 'idempotent_id' must be provided for specific operations, otherwise the node will throw an error.
  • If the API base URL is changed, ensure it is correct to avoid connection errors.

Links

Discussion