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 Pix Checkout, specifically generating a checkout request for Pix payments. It is useful for automating payment collection via Pix by creating a checkout session that can be shared with customers. For example, an e-commerce platform can use this node to generate a Pix checkout link or QR code for customers to complete their payments.

Use Case Examples

  1. Creating a Pix checkout session with an expiration time and external reference for tracking.
  2. Adding optional generator name and document details to customize the checkout.
  3. Including a webhook URL to receive payment notifications automatically.

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.
Additional Fields Optional parameters to customize the checkout, such as generator name, document, external reference, expiration time, external link, filters, webhook URL and type, authorization header for webhook, and payment authorization status.
Required Fields (JSON) JSON object containing the required fields for the checkout creation request, as per Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing details of the created Pix checkout.

Dependencies

  • Zendry API access via a valid Bearer token

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to create Pix checkouts.
  • The requestBody must be a valid JSON string; invalid JSON will cause an error.
  • Required fields for the Pix checkout must be included in the requestBody JSON; missing required fields will cause the API to reject the request.
  • If using webhooks, ensure the webhook URL and type ID are correctly set and accessible.
  • Common error messages include invalid token, missing required parameters, or invalid JSON format. Verify all inputs accordingly.

Links

Discussion