Actions18
- Receipts (Pix) Actions
- Payments (Pix Out) Actions
- Webhooks Actions
- Crypto Actions
- Account Actions
- Checkout Actions
Overview
This node integrates with the Zendry API to perform operations related to Pix Out payments, specifically listing payments. It is useful for users who want to retrieve a list of Pix payment transactions made through the Zendry platform. For example, a business could use this node to fetch recent payment records for reconciliation or reporting purposes.
Use Case Examples
- List all Pix Out payments made within a certain period to generate a financial report.
- Fetch payment details to verify transaction statuses in an automated workflow.
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/pix/payments for listing payments. Required if no predefined operation is selected. |
| HTTP Method | HTTP method to use for the API request (GET, POST, PUT, PATCH, DELETE). Defaults to GET for listing payments. |
| Body (JSON) | Request body in JSON format, used for non-GET requests to send data to the API. |
Output
JSON
json- The JSON response from the Zendry API containing the list of payments or error information.
Dependencies
- Zendry API authentication using Client ID and Client Secret to obtain a Bearer token.
Troubleshooting
- Ensure Client ID and Client Secret are correctly provided; missing credentials will cause authentication errors.
- Verify the API endpoint and HTTP method are correct, especially if using a custom endpoint instead of predefined operations.
- If using a request body, ensure it is valid JSON to avoid parsing errors.
- Common error messages include token retrieval failures and invalid JSON body errors; check credentials and JSON formatting respectively.
Links
- Zendry API Documentation - Official documentation for Zendry API endpoints and usage.