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 provides universal access to the Zendry API, enabling operations across multiple resources such as Pix receipts, payments, webhooks, account information, cryptocurrency transactions, and checkout processes. Specifically, for the 'Account' resource and 'Get USDT Quotation' operation, it fetches the current USDT cryptocurrency quotation from the Zendry API. This node is useful for automating financial workflows, retrieving real-time cryptocurrency prices, managing Pix payments, and handling webhooks within the Zendry ecosystem.

Use Case Examples

  1. Fetch the current USDT quotation to update pricing in a financial dashboard.
  2. Retrieve account balance and cryptocurrency quotations for portfolio management.
  3. Automate Pix payment creation and tracking using the Zendry API.

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; usually defaults to https://api.zendry.com.br and should not be changed unless necessary.
Additional Fields Optional parameters that can be added depending on the resource and operation, such as generator name, document, external references, expiration time, filters, webhook URLs, and authorization headers.
Required Fields (JSON) JSON object containing required fields for the selected operation, as specified by the Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing data relevant to the requested operation, such as USDT quotation details for the 'Get USDT Quotation' operation.

Dependencies

  • Requires a valid Bearer access token for the Zendry API to authenticate requests.

Troubleshooting

  • Ensure the Access Token is valid and has not expired; invalid tokens will cause authentication errors.
  • The 'requestBody' field must contain valid JSON; malformed JSON will cause parsing errors.
  • Required parameters for specific operations must be provided, e.g., 'end_to_end' for 'Get by EndToEnd' or 'reference_id' for 'payQr'; missing these will cause errors.
  • Network issues or incorrect Base URL configuration can lead to request failures.

Links

  • Zendry API Documentation - Official documentation for the Zendry API, detailing available resources, operations, and required parameters.

Discussion