Zendry Global API 1.0 icon

Zendry Global API 1.0

Acesso universal à API Zendry (Pix, Payments, Webhooks, Account, Crypto, Checkout) via AccessToken

Actions120

Overview

This node integrates with the Zendry API to create a payment using the DICT initiation type within the Checkout resource. It is useful for automating payment creation in systems that support Pix payments in Brazil, allowing users to programmatically initiate payments with optional parameters such as authorization status and external references. For example, it can be used in e-commerce platforms to trigger Pix payments automatically upon order confirmation.

Use Case Examples

  1. Creating a Pix payment with DICT initiation by providing required payment details in JSON format along with an access token.
  2. Adding optional fields like authorization status or external reference to track payments.
  3. Using the node to automate payment creation workflows in financial or billing systems.

Properties

Name Meaning
Access Token A valid Bearer access token for authenticating requests to 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 payment creation, such as generator name, document, external reference, expiration time, external link, filters, webhook settings, and authorization status.
Required Fields (JSON) JSON object containing the required fields for the payment creation operation as per the API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing details of the created payment 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 (JSON)' input, and missing mandatory parameters such as reference codes or IDs for specific operations.
  • Error messages related to invalid JSON indicate that the 'Required Fields (JSON)' input must be a valid JSON string or object.
  • Errors about missing required parameters (e.g., 'reference_id', 'end_to_end') mean those fields must be provided either in the JSON body or additional fields.
  • Ensure the base URL is correct and the API endpoint supports the requested operation to avoid unsupported resource or operation errors.

Discussion