Zendry Global API 1.0 icon

Zendry Global API 1.0

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

Actions120

Overview

This node integrates with the Zendry API to perform various operations related to Webhooks, Pix payments, account management, crypto transactions, and checkout processes. Specifically, for the 'Webhooks' resource and 'Generate Checkout' operation, it allows users to generate a checkout charge via the Zendry API. This is useful for automating payment processing and checkout generation in workflows, such as creating payment requests or managing webhook notifications for payment events.

Use Case Examples

  1. Generate a checkout charge for a customer using the Zendry API by providing the required charge details in JSON format.
  2. Register or update webhook URLs to receive notifications about payment events.
  3. List available webhook types or existing webhooks for monitoring and management.

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 URL, webhook type ID, authorization header value, and payment authorization status.
Required Fields (JSON) JSON object containing the required fields for the specific operation, 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 checkout charge details or webhook registration status.

Dependencies

  • Requires a valid Zendry API access token for authentication.

Troubleshooting

  • Ensure the 'Access Token' is valid and has the necessary permissions for the requested operation.
  • Verify that the 'requestBody' JSON is correctly formatted and contains all required fields as per the Zendry API documentation.
  • Check that mandatory parameters like 'webhook_type_id' and 'url' are provided when registering or updating webhooks.
  • Handle API errors gracefully by enabling 'Continue On Fail' to avoid workflow interruptions.

Links

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

Discussion