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 API to perform various operations related to webhooks, payments, receipts, accounts, crypto, and checkout services. Specifically, for the 'Webhooks' resource and 'List Webhooks' operation, it retrieves a list of registered webhooks from the Zendry API. This is useful for users who want to manage or monitor their webhook configurations programmatically, such as viewing all active webhooks for notification purposes or integration management.

Use Case Examples

  1. A user wants to fetch all webhooks registered in their Zendry account to verify which URLs are currently set to receive notifications.
  2. An automation workflow needs to list webhooks to dynamically adjust or audit webhook endpoints based on current configurations.

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, including filters and webhook-specific fields such as webhook URL, webhook type ID, authorization header value, and authorization status.
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 webhooks or other requested data.

Dependencies

  • Requires a valid Bearer access token for Zendry API authentication.

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to access webhook data.
  • Verify that the Base URL is correct and reachable; the default is https://api.zendry.com.br.
  • If using filters in Additional Fields, ensure the JSON is valid to avoid parsing errors.
  • Common errors include missing required parameters such as webhook_type_id or url when registering or removing webhooks; these must be provided to avoid operation errors.
  • Network or API errors will be thrown as NodeOperationError with details; check the error message for guidance.

Links

Discussion