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 Webhooks, Pix QR Codes, Payments, Account information, Crypto transactions, and Checkout processes. Specifically, for the 'Webhooks' resource and '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 for Pix transactions, commonly used in Brazil for instant payments.

Use Case Examples

  1. Generating a Pix QR Code for a payment request with optional metadata such as generator name, document, expiration time, and external references.
  2. Creating a webhook to receive notifications about Pix payment events by specifying the webhook URL and type.

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 or webhook registration, such as generator name, document, expiration time, external references, webhook URL, webhook type ID, authorization header, and payment authorization status.
Required Fields (JSON) JSON object containing required fields for the specific operation, such as QR Code creation parameters.

Output

JSON

  • json - The JSON response from the Zendry API containing the result of the requested operation, such as the created QR Code details or webhook registration confirmation.

Dependencies

  • Requires a valid Zendry API access token for authentication.

Troubleshooting

  • Ensure the access token is valid and has the necessary permissions for the requested operation.
  • Verify that required fields in the JSON request body are correctly formatted and include all mandatory parameters.
  • Check that the webhook_type_id and URL are provided when registering or removing webhooks.
  • Handle JSON parsing errors in the 'requestBody' and 'filters' fields by ensuring valid JSON syntax.

Links

Discussion