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 interacts with the Zendry Global API to perform various operations related to webhooks, payments, Pix receipts, accounts, crypto, and checkout services. Specifically, for the 'Webhooks' resource and 'List Webhook Types' operation, it retrieves a list of available webhook types from the Zendry API. This is useful for users who want to manage or monitor webhook configurations programmatically, such as listing all webhook types to understand what events can be subscribed to.

Use Case Examples

  1. A user wants to list all webhook types supported by Zendry to configure webhook listeners accordingly.
  2. A developer integrates this node in an automation workflow to dynamically fetch webhook types before registering new webhooks.

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 can be changed if necessary.
Additional Fields Optional parameters that can be used for various operations, including webhook-related fields such as webhook URL, webhook type ID, authorization header value, and others.
Required Fields (JSON) JSON object containing required fields for the operation as per the API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the list of webhook types or other requested data.

Dependencies

  • Zendry API

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to access the Zendry API.
  • Verify that the Base URL is correct and reachable from the environment where the node is running.
  • If the requestBody JSON is malformed, the node will throw an error indicating invalid JSON; ensure the JSON is properly formatted.
  • For operations requiring specific IDs (e.g., webhook_type_id), ensure these are provided either in the requestBody or additionalFields.
  • Network issues or API downtime can cause request failures; check network connectivity and Zendry API status.

Links

Discussion