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 Reference Code' operation, it retrieves payment details using a unique reference code. This is useful for tracking and verifying payments made via Pix using a known reference code. Practical applications include financial reconciliation, payment status checks, and automated payment processing workflows.

Use Case Examples

  1. Retrieve payment details by providing a valid reference code to confirm payment status.
  2. Use the node to automate payment verification in an e-commerce system that accepts Pix payments.

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, such as the reference code for payment retrieval.

Output

JSON

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

Dependencies

  • Zendry API access requiring a valid Bearer access token.

Troubleshooting

  • Common errors include missing or invalid 'reference_code' which is mandatory for the 'Get Payment by Reference Code' operation. Ensure the reference code is provided either in the required JSON fields or additional fields.
  • Invalid or expired access tokens will cause authentication failures. Verify the token is current and correctly formatted as a Bearer token.
  • Malformed JSON in the 'Required Fields (JSON)' input will cause parsing errors. Ensure the JSON is valid before execution.

Links

Discussion