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, payments, Pix QR codes, webhooks, crypto payments, and checkout charges. Specifically, for the 'Account' resource and 'List Payments' operation, it retrieves a list of payments made via Pix. This is useful for financial reconciliation, monitoring payment statuses, or integrating payment data into other workflows. For example, a business can use this node to automatically fetch recent payment transactions and update their accounting system.

Use Case Examples

  1. A business uses the node to list all Pix payments received within a certain period to reconcile their accounts.
  2. A developer integrates the node to fetch payment data and trigger notifications or further processing based on payment status.

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; usually left as default unless a custom endpoint is needed.
Additional Fields Optional parameters to refine or filter the payments 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 Zendry API documentation.

Output

JSON

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

Dependencies

  • Zendry API access with a valid Bearer access token

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to access payment data.
  • Verify that the 'filters' JSON in Additional Fields is correctly formatted to avoid JSON parsing errors.
  • If required fields in the JSON request body are missing or malformed, the API will return errors; ensure compliance with Zendry API documentation.
  • Network or API endpoint issues can cause request failures; check the Base URL and network connectivity.

Links

Discussion