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 perform various operations related to cryptocurrency, payments, webhooks, accounts, and checkouts. Specifically, for the 'Crypto' resource and 'Generate Checkout' operation, it sends a POST request to generate a checkout charge via the Zendry API. This is useful for automating payment processing and checkout generation in applications that use Zendry's services, such as e-commerce platforms or financial service tools.

Use Case Examples

  1. Generate a crypto payment checkout charge by providing the required JSON payload and optional additional fields like generator name or expiration time.
  2. Automate the creation of checkout charges for cryptocurrency transactions using the Zendry API within an n8n workflow.

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 request, such as generator name, document, external reference, expiration time, external link, filters, webhook settings, and authorization headers.
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 generate checkout charge operation.

Dependencies

  • Zendry API access requiring a valid Bearer access token

Troubleshooting

  • Ensure the 'Access Token' is valid and has the necessary permissions to perform the operation.
  • Verify that the 'Required Fields (JSON)' input is a valid JSON string and contains all mandatory fields as per the Zendry API documentation.
  • Check that the 'Base URL' is correct and accessible; the default is https://api.zendry.com.br and should not be changed unless necessary.
  • If the node throws errors about missing required parameters (e.g., webhook_type_id, url), ensure these are provided in the additional fields or request body as required.
  • For JSON parsing errors, confirm that the JSON inputs are properly formatted and valid.

Links

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

Discussion