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 manage Pix Out payments and related operations. Specifically, the 'Get by EndToEnd' operation retrieves payment information using the unique 'end_to_end' identifier of a Pix QR code. This is useful for tracking and verifying payments made via Pix by referencing their end-to-end transaction ID. Practical applications include financial reconciliation, payment status checks, and automated payment processing workflows.

Use Case Examples

  1. Retrieve payment details by providing the 'end_to_end' ID of a Pix QR code to verify if a payment was completed.
  2. Use the node in a workflow to automatically fetch payment information after a Pix transaction is initiated, enabling real-time updates in accounting systems.

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 customize the request, such as generator name, document, external references, expiration time, filters, webhook settings, and authorization headers.
Required Fields (JSON) JSON object containing required fields for the specific operation, such as the 'end_to_end' identifier for the 'Get by EndToEnd' operation.

Output

JSON

  • json - The JSON response from the Zendry API containing payment details or error information.

Dependencies

  • Requires a valid Zendry API access token for authentication.

Troubleshooting

  • Ensure the 'end_to_end' field is provided and correctly formatted; missing this field will cause an error.
  • Verify the access token is valid and has not expired to avoid authentication errors.
  • Check that the base URL is correct and accessible; network issues or incorrect URLs will cause request failures.
  • If the requestBody JSON is malformed, the node will throw a JSON parsing error; ensure valid JSON syntax.

Links

Discussion