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 integrates with the Zendry API to perform various operations related to cryptocurrency payments, Pix payments, webhooks, account information, and checkout processes. Specifically, for the 'Crypto' resource and 'Create Payment (DICT)' operation, it allows users to create a cryptocurrency payment using the DICT initiation type. This is useful for automating payment creation in financial applications, enabling seamless interaction with the Zendry payment infrastructure.

Use Case Examples

  1. Creating a DICT payment for a cryptocurrency transaction by providing required payment details in JSON format along with optional additional fields like authorization status.
  2. Automating payment workflows in a financial system that uses Zendry API for payment processing.

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.
Additional Fields Optional parameters to customize the payment creation, such as generator name, document, external reference, expiration time, external link, filters, webhook settings, and authorization status.
Required Fields (JSON) JSON object containing the required fields for the payment creation operation as per Zendry API documentation.

Output

JSON

  • json - The JSON response from the Zendry API containing details of the created payment or other requested data.

Dependencies

  • Zendry API

Troubleshooting

  • Ensure the Access Token is valid and has the necessary permissions to perform the operation.
  • Verify that the JSON provided in 'Required Fields (JSON)' is correctly formatted and contains all mandatory fields as per the Zendry API documentation.
  • Check that required parameters like 'reference_code', 'idempotent_id', or 'webhook_type_id' are provided when needed, otherwise the node will throw an error indicating the missing parameter.
  • If the base URL is changed, ensure it points to a valid Zendry API endpoint.

Links

Discussion