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 interacts with the Zendry API to generate a checkout charge for payments (Pix Out). It is designed to facilitate the creation of payment charges via the Zendry platform, allowing users to specify required and optional parameters for the checkout process. This node is useful in scenarios where automated payment processing and checkout generation are needed, such as e-commerce platforms or financial services integrating Pix payment methods.

Use Case Examples

  1. Generate a Pix checkout charge with specific payment details and expiration time.
  2. Create a checkout charge with an external reference for tracking purposes.

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 generation, such as generator name, document, external reference, expiration time, external link, filters, webhook settings, and authorization headers.
Required Fields (JSON) JSON object containing the required fields for the checkout charge operation as per Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing details of the generated checkout charge.

Dependencies

  • Requires a valid Zendry API access token for authentication.

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to perform the operation.
  • The 'requestBody' must be a valid JSON string; invalid JSON will cause an error.
  • Required fields for the checkout charge must be provided in the 'requestBody' JSON; missing required fields will cause the API to reject the request.
  • If optional fields are provided, ensure they conform to expected types and formats, e.g., expiration time as a number, filters as valid JSON.
  • Network or API endpoint issues may cause request failures; verify the Base URL and network connectivity.

Discussion