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, accounts, and checkouts. Specifically, the 'Get Payment by Idempotent ID' operation retrieves payment details using a unique idempotent ID, ensuring idempotency in payment processing. This node is useful for automating payment retrievals, tracking payment statuses, and integrating payment data into workflows. For example, it can be used to fetch payment information after a transaction to update order statuses or trigger notifications.

Use Case Examples

  1. Retrieve payment details by idempotent ID to confirm transaction status in an e-commerce workflow.
  2. Automate reconciliation processes by fetching payment data using idempotent IDs to avoid duplicate processing.

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 to customize the request, such as generator name, document, external reference, expiration time, external link, filters in JSON format, webhook URL and type, authorization header for webhooks, and payment authorization status.
Required Fields (JSON) JSON object containing required fields for the operation, as specified by the Zendry API documentation.

Output

JSON

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

Dependencies

  • Requires a valid Zendry API access token for authentication.

Troubleshooting

  • Ensure the 'accessToken' is valid and has the necessary permissions to access the Zendry API.
  • Verify that the 'idempotent_id' parameter is provided and correctly formatted for the 'Get Payment by Idempotent ID' operation; missing this will cause an error.
  • Check that the 'requestBody' JSON is valid and correctly structured according to the API documentation to avoid JSON parsing errors.
  • If the base URL is changed, ensure it points to a valid Zendry API endpoint to prevent connection errors.

Links

Discussion