Zendry Global API 1.0 icon

Zendry Global API 1.0

Acesso universal à API Zendry (Pix, Payments, Webhooks, Account, Crypto, Checkout) via AccessToken

Actions120

Payments (Pix Out) → Generate Crypto Payment

AI-generated

Overview

This node integrates with the Zendry API to perform various operations related to payments, Pix transactions, webhooks, account information, cryptocurrency payments, and checkout processes. Specifically, for the 'Payments (Pix Out)' resource and the 'Generate Crypto Payment' operation, it allows users to create cryptocurrency payment requests by sending the required JSON payload to the Zendry API. This node is useful for automating payment generation workflows, tracking payments, and integrating crypto payment capabilities into broader automation processes.

Use Case Examples

  1. Generating a crypto payment request by providing the necessary payment details in JSON format.
  2. Automating the creation of Pix payments and managing payment authorizations.
  3. Setting up webhooks to receive notifications about payment status changes.

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 that can be added to the request, 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) The required JSON payload for the operation, containing mandatory fields as per the Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the result of the requested operation, such as details of the generated crypto payment.

Dependencies

  • Requires a valid Bearer access token for the Zendry API.

Troubleshooting

  • Ensure the 'requestBody' JSON is valid and correctly formatted; invalid JSON will cause errors.
  • Mandatory fields like 'webhook_type_id', 'url', 'reference_id', 'end_to_end', 'reference_code', or 'idempotent_id' must be provided for their respective operations, otherwise the node will throw an error.
  • Check that the Access Token is valid and has the necessary permissions to perform the requested operation.
  • If the API base URL is changed, verify it is correct to avoid connection errors.

Links

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

Discussion