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 cryptocurrency payments, Pix payments, webhooks, account information, and checkout processes. Specifically, for the 'Crypto' resource and 'Get Payment by Reference Code' operation, it retrieves payment details using a reference code. This node is useful for automating payment retrievals, tracking transactions, and integrating payment data into workflows. For example, it can be used to fetch payment status or details by providing a reference code, enabling automated payment verification or reconciliation.

Use Case Examples

  1. Retrieve payment details by reference code to verify payment status in an automated billing system.
  2. Fetch payment information for a specific transaction to update customer records or trigger follow-up actions.

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 the API documentation.

Output

JSON

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

Dependencies

  • Zendry API (requires a valid Bearer access token)

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 accessible from the environment where the node runs.
  • 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