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 the Checkout resource, specifically including the operation to get payment details by a reference code. It is useful for retrieving payment information in scenarios where you have a payment reference code and need to fetch the associated payment data from Zendry's system. Practical examples include verifying payment status or details in an automated workflow after a payment is made.

Use Case Examples

  1. Retrieve payment details by providing a payment reference code to confirm transaction status.
  2. Use the node to fetch payment information for reconciliation or reporting purposes in financial workflows.

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, which should not be changed unless necessary.
Additional Fields Optional parameters that can be added to the 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 payment details or other requested data.

Dependencies

  • Zendry API

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to access the Zendry API.
  • Verify that the reference_code parameter is provided and correctly formatted for the 'Get Payment by Reference Code' operation.
  • Check that the Base URL is correct and reachable from the environment where the node is running.
  • If the requestBody JSON is malformed, the node will throw an error; ensure it is valid JSON.
  • Handle API errors gracefully by enabling 'Continue On Fail' if partial processing is acceptable.

Links

Discussion