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 cryptocurrencies, Pix payments, webhooks, account information, and unified checkout. Specifically, for the 'Crypto Receivement' operation under the 'Crypto' resource, it simulates a cryptocurrency receivement (staging environment). This node is useful for automating and managing crypto transactions, generating payments, wallets, and quotations, as well as handling Pix QR codes and payments. For example, it can simulate receiving USDT cryptocurrency payments in a test environment.

Use Case Examples

  1. Simulate receiving a USDT payment in a staging environment to test payment workflows.
  2. Generate a crypto wallet or payment request for USDT.
  3. Retrieve cryptocurrency quotations for USDT.

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 when no predefined operation is selected. For 'Crypto Receivement', this is predefined and usually not required to be set manually.
HTTP Method HTTP method to use for the API request when no predefined operation is selected. For 'Crypto Receivement', this is predefined as POST.
Body (JSON) JSON formatted request body to send with the API call, required for POST requests like 'Crypto Receivement'.

Output

JSON

  • json - The JSON response from the Zendry API for the requested operation, e.g., details of the simulated crypto receivement.

Dependencies

  • Requires Zendry API credentials: Client ID and Client Secret for authentication.

Troubleshooting

  • Ensure that Client ID and Client Secret are correctly provided; missing credentials will cause authentication errors.
  • The request body must be valid JSON when required; invalid JSON will cause errors.
  • If the API endpoint or HTTP method is not predefined and not provided manually, the node will throw an error.
  • Token retrieval errors may occur if the Zendry API is unreachable or credentials are invalid.

Links

Discussion