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 integrates with the Zendry API to create a Pix payment using the DICT method. It allows users to send payment requests to the Zendry platform by providing necessary payment details in JSON format along with optional additional fields. This node is useful for automating Pix payment creation in financial workflows, such as invoicing systems or payment processing applications.

Use Case Examples

  1. Creating a Pix payment by providing payment details like amount, recipient information, and optional authorization status.
  2. Automating payment creation in a billing system by sending payment requests to Zendry API with custom external references for tracking.

Properties

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

Output

JSON

  • json - Response from the Zendry API containing details of the created Pix payment or error information.

Dependencies

  • Zendry API access with a valid Bearer token

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to create Pix payments.
  • Verify that the JSON provided in 'Required Fields (JSON)' is correctly formatted and contains all mandatory fields as per Zendry API documentation.
  • Check that required parameters like 'reference_code' or 'idempotent_id' are provided when needed for specific operations.
  • If the node throws errors about unsupported resources or operations, confirm that the selected resource and operation match the node's capabilities.

Links

Discussion