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 perform various operations related to the Checkout resource, specifically generating crypto payments. It is useful for automating cryptocurrency payment generation within workflows, allowing users to create crypto payment requests programmatically. For example, it can be used to generate a crypto payment request for a customer during an e-commerce checkout process.

Use Case Examples

  1. Generate a crypto payment request by providing the required JSON payload and access token to the Zendry API.
  2. Automate the creation of crypto payments in a payment processing 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.
Additional Fields Optional parameters 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 payload containing the required fields for the operation as per the API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the result of the crypto payment generation request.

Dependencies

  • Zendry API access requiring a valid Bearer access token.

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to call the Zendry API.
  • Verify that the JSON provided in the Required Fields is valid and contains all mandatory fields as per the Zendry API documentation.
  • Check the Base URL is correct and reachable; the default is https://api.zendry.com.br.
  • Common error messages include missing required parameters such as webhook_type_id, url, reference_id, or end_to_end depending on the operation. Ensure these are provided when required.
  • If the node throws a JSON parsing error, verify that the JSON input is correctly formatted.

Discussion