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, and checkout services. Specifically, for the 'Account' resource and 'Get Payment by Reference Code' operation, it retrieves payment details using a unique reference code. This is useful for tracking and verifying payments made via Pix or other supported payment methods. Practical examples include fetching payment status for reconciliation or auditing purposes.

Use Case Examples

  1. Retrieve payment details by providing a valid reference code to confirm payment completion.
  2. Use the node to automate payment verification in financial workflows by fetching payment data from Zendry API.

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 customize the request, such as generator name, document, external reference, expiration time, external link, filters, webhook settings, and authorization headers.
Required Fields (JSON) JSON object containing required fields for the specific operation, as per Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the requested payment details or other resource data.

Dependencies

  • Requires a valid Zendry API access token for authentication.

Troubleshooting

  • Ensure the access token is valid and has not expired to avoid authentication errors.
  • Verify that the reference_code parameter is provided and correctly formatted; missing or invalid reference_code will cause errors.
  • Check that the base URL is correct and accessible; network issues or incorrect URLs will prevent API communication.
  • If using additional fields with JSON filters, ensure the JSON is valid to avoid parsing errors.
  • Handle API rate limits or downtime by implementing retry logic or error handling in workflows.

Links

Discussion