Zendry Global API 1.0 icon

Zendry Global API 1.0

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

Actions120

Payments (Pix Out) → Remove Webhook

AI-generated

Overview

This node interacts with the Zendry API to manage various payment-related operations, specifically for the 'Payments (Pix Out)' resource with the 'Remove Webhook' operation. It allows users to remove a registered webhook by specifying the webhook type ID. This is useful for managing webhook subscriptions and stopping notifications for certain webhook types. For example, if a user no longer wants to receive payment notifications via a specific webhook, they can use this node to remove that webhook from the Zendry system.

Use Case Examples

  1. Removing a webhook subscription for payment notifications by providing the webhook type ID to stop receiving updates.
  2. Managing webhook lifecycle by programmatically removing webhooks when they are no longer needed.

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 including webhook_type_id (ID of the webhook type to remove) and other webhook-related fields, though only webhook_type_id is required for removal.
Required Fields (JSON) JSON object containing required fields for the operation, though for removal this is typically empty or minimal.

Output

JSON

  • json - The JSON response from the Zendry API after attempting to remove the webhook, indicating success or failure details.

Dependencies

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

Troubleshooting

  • Common issues include missing or invalid webhook_type_id, which will cause the node to throw an error indicating the required field is missing.
  • Invalid or expired access tokens will result in authentication errors from the Zendry API.
  • Malformed JSON in the 'Required Fields (JSON)' input will cause parsing errors; ensure valid JSON is provided if used.

Links

Discussion