Zendry Global API 1.0 icon

Zendry Global API 1.0

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

Actions120

Webhooks → Get USDT Quotation

AI-generated

Overview

This node provides access to the Zendry Global API, enabling interaction with various Zendry services such as Pix receipts, payments, webhooks, account information, cryptocurrency operations, and checkout processes. Specifically, the 'Get USDT Quotation' operation under the 'Webhooks' resource fetches the current USDT (Tether) cryptocurrency quotation from the Zendry API. This node is useful for automating financial workflows, monitoring cryptocurrency prices, managing payment webhooks, and integrating Zendry's payment and crypto services into automation pipelines.

Use Case Examples

  1. Fetch the latest USDT quotation to update a financial dashboard.
  2. Use the node to trigger actions based on cryptocurrency price changes.
  3. Integrate with Zendry's webhook system to automate payment notifications.

Properties

Name Meaning
Access Token A valid Bearer access token for authenticating requests to the Zendry API.
Base URL The base URL of the Zendry API; usually left as the default unless a custom endpoint is needed.
Additional Fields Optional parameters that can be added to the request, such as generator name, document, external references, expiration time, filters, webhook URL, webhook type ID, authorization header value, and payment authorization status.
Required Fields (JSON) JSON object containing required fields for the specific operation, as per Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the requested data, such as the USDT quotation details.

Dependencies

  • Requires a valid Zendry API access token for authentication.

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions; invalid tokens will cause authentication errors.
  • The 'requestBody' must be a valid JSON string; invalid JSON will cause parsing errors.
  • Required parameters like 'webhook_type_id' or 'url' must be provided for webhook operations; missing these will cause errors.
  • Network or API endpoint issues may cause request failures; verify the Base URL and network connectivity.

Links

Discussion