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 Global API to perform various operations related to cryptocurrency payments, Pix payments, webhooks, account information, and checkout processes. Specifically, for the 'Crypto' resource and 'List Payments' operation, it retrieves a list of cryptocurrency payments from the Zendry API. This node is useful for automating payment retrieval, tracking payment statuses, and integrating payment data into workflows. For example, it can be used to fetch recent crypto payments for reconciliation or reporting purposes.

Use Case Examples

  1. Fetch a list of all cryptocurrency payments made within a certain period to update a financial dashboard.
  2. Retrieve payment details to trigger follow-up actions such as sending confirmation emails or updating order statuses.

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; usually left as default unless a custom endpoint is needed.
Additional Fields Optional parameters to filter or customize the payments listing, such as filters in JSON format or authorization flags.
Required Fields (JSON) JSON object containing required fields for the operation as per API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing the list of cryptocurrency payments and related data.

Dependencies

  • Zendry API access requiring a valid Bearer access token.

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to access the Crypto payments endpoint.
  • Verify that the JSON provided in 'Required Fields' and 'Filters' is correctly formatted to avoid parsing errors.
  • Check the Base URL if using a custom endpoint to ensure it is reachable and correct.
  • Common error messages include missing required parameters like 'reference_code' or 'idempotent_id' for specific operations; ensure these are provided when needed.

Links

Discussion