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 Pix payments, receipts, webhooks, account information, crypto transactions, and checkout processes. Specifically, for the 'Payments (Pix Out)' resource and the 'Get Payment by Idempotent ID' operation, it retrieves payment details using a unique idempotent ID. This is useful for ensuring idempotent payment retrievals in financial workflows, avoiding duplicate processing. Practical examples include fetching payment status or details after initiating a Pix payment to confirm transaction completion or for reconciliation purposes.

Use Case Examples

  1. Retrieve payment details by idempotent ID to verify payment status in a financial automation workflow.
  2. Use the node to fetch payment information for audit or reporting purposes based on the idempotent ID.

Properties

Name Meaning
Access Token Bearer token for authenticating API requests to Zendry.
Base URL Base URL of the Zendry API, defaulting to https://api.zendry.com.br.
Additional Fields Optional parameters to customize the API 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 operation as per API documentation.

Output

JSON

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

Dependencies

  • Requires a valid Bearer access token for Zendry API authentication.

Troubleshooting

  • Common issues include invalid or missing access tokens, malformed JSON in the 'Required Fields' input, and missing mandatory parameters such as 'idempotent_id' for this operation.
  • Error messages typically indicate missing required parameters or invalid JSON format. Ensure the 'idempotent_id' is provided either in the 'Required Fields' JSON or in the 'Additional Fields'.
  • If the API returns an error, verify the access token validity and the correctness of the base URL.

Links

Discussion