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 perform various operations related to Pix payments, receipts, webhooks, account information, cryptocurrency, and checkout processes. Specifically, for the Payments (Pix Out) resource with the Create QRCode (Pix) operation, it allows users to create Pix QR codes by sending a POST request to the Zendry API. This is useful for generating payment QR codes that can be scanned by customers to make Pix payments. Practical applications include automating payment collection in e-commerce, retail, or service environments where Pix is a payment method.

Use Case Examples

  1. Generate a Pix QR code for a customer to scan and pay.
  2. Create a checkout Pix QR code with optional expiration and external references for tracking.

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, 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, external link for checkout, filters in JSON format, webhook URL and type, authorization header for webhook, and payment authorization status.
Required Fields (JSON) A JSON object containing the required fields for the operation as per the Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the result of the QR code creation or other requested operation.

Dependencies

  • Zendry API

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to perform the operation.
  • Verify that the JSON provided in the Required Fields is correctly formatted and includes all mandatory fields as per the Zendry API documentation.
  • Check that mandatory parameters like reference IDs or webhook type IDs are provided when required, otherwise the node will throw an error.
  • If the base URL is changed, ensure it points to a valid Zendry API endpoint.

Links

Discussion