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 perform various operations related to Pix payments, webhooks, account management, cryptocurrency transactions, and checkout processes. Specifically, for the 'Crypto' resource and 'Create QRCode (Pix)' operation, it allows users to create a Pix QR code by sending a POST request to the Zendry API with required and optional parameters. This is useful for generating payment QR codes for Pix transactions, which can be used in payment processing systems or financial applications.

Use Case Examples

  1. Generating a Pix QR code for a payment request with optional metadata such as generator name and document, expiration time, and external references.
  2. Creating a QR code to facilitate instant payments via Pix in a financial app or e-commerce platform.

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 QR code creation, such as generator name, generator document (CPF/CNPJ), external reference, expiration time in seconds, and other webhook or authorization details.
Required Fields (JSON) A JSON object containing the required fields for the operation, as specified by the Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing details of the created QR code or other requested data.

Dependencies

  • Zendry API access requiring a valid Bearer access token

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to perform the operation.
  • Verify that the JSON provided in 'Required Fields (JSON)' is correctly formatted and includes all mandatory fields as per the Zendry API documentation.
  • Check that required parameters like 'reference_id' or 'end_to_end' are provided when needed for specific operations.
  • If the node throws an error about unsupported resources or operations, confirm that the selected resource and operation are valid and supported by the node.

Links

  • Zendry API Documentation - Official documentation for the Zendry API, detailing endpoints, required fields, and usage examples.

Discussion