Zendry API icon

Zendry API

Integração com Zendry API (Pix, Payments, Webhooks, Account, Crypto, Checkout)
Join our community

Actions18

Overview

This node integrates with the Zendry API to perform various operations related to cryptocurrency payments, Pix payments, webhooks, account information, and unified checkout. Specifically, for the Crypto resource and Crypto Payment operation, it generates a USDT cryptocurrency payment. It is useful for automating payment processing workflows involving cryptocurrencies and Pix transactions, such as generating crypto payment requests or managing crypto wallets.

Use Case Examples

  1. Generate a USDT crypto payment request to send to a customer.
  2. Create and manage cryptocurrency wallets for receiving payments.
  3. Fetch cryptocurrency quotations for USDT to display current rates.

Properties

Name Meaning
Client ID Client ID of the Zendry application, used for API authentication.
Client Secret Client Secret of the Zendry application, used for API authentication.
Endpoint API endpoint to call, e.g., /v1/crypto/payment for crypto payment operation. Required if no predefined operation is selected.
HTTP Method HTTP method to use for the API request (GET, POST, PUT, PATCH, DELETE). Required if no predefined operation is selected.
Body (JSON) Request body in JSON format, used for POST, PUT, PATCH requests to send data to the API.

Output

JSON

  • json - The JSON response from the Zendry API for the requested operation, such as details of the crypto payment generated.

Dependencies

  • Zendry API with Client ID and Client Secret for authentication

Troubleshooting

  • Ensure Client ID and Client Secret are correctly provided; missing these will cause authentication errors.
  • The request body must be valid JSON when sending data; invalid JSON will cause errors.
  • If no predefined operation is selected, the Endpoint and HTTP Method must be specified; otherwise, the node will throw an error.
  • API token retrieval errors may occur if credentials are invalid or network issues happen; verify credentials and connectivity.

Links

Discussion