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 list webhook types related to payments (Pix Out). It is useful for users who want to retrieve available webhook event types that can be registered for notifications. For example, a user can list webhook types to understand what events can trigger notifications for Pix Out payments, enabling automation or monitoring workflows based on payment events.

Use Case Examples

  1. A user wants to automate their payment processing system by receiving notifications when certain payment events occur. They use this node to list all webhook types available in the Zendry API to decide which webhook to register.
  2. A developer building a payment dashboard uses this node to fetch webhook types to display options for webhook configuration in their application.

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 provided for the operation, such as webhook_type_id, webhook URL, authorization header value, and other filters or metadata.
Required Fields (JSON) JSON object containing required fields for the operation, if any (not typically required for listing webhook types).

Output

JSON

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

Dependencies

  • Zendry API

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to access webhook types.
  • Verify the Base URL is correct and reachable from the environment where the node runs.
  • If the requestBody JSON is malformed, the node will throw an error indicating invalid JSON; ensure proper JSON formatting.
  • If required parameters like webhook_type_id or URL are missing for other webhook operations, the node will throw errors specifying the missing fields.

Links

Discussion