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 receipts, specifically allowing users to retrieve receipt information by the 'end_to_end' identifier. It is useful for scenarios where you need to query Pix QR code payment details using a unique transaction identifier. For example, a business can use this node to verify payment status or details of a Pix transaction by providing the end-to-end ID.
Use Case Examples
- Retrieve Pix receipt details by providing the 'end_to_end' ID to confirm payment status.
- Use in automated workflows to fetch transaction information for reconciliation or reporting.
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/qrcodes/end_to_end. Required if no predefined operation is selected. |
| HTTP Method | HTTP method for the API request (GET, POST, PUT, PATCH, DELETE). Defaults to GET. |
| Body (JSON) | Request body in JSON format, used for non-GET requests. |
Output
JSON
json- The JSON response from the Zendry API containing the requested Pix receipt data or error information.
Dependencies
- Requires Zendry API credentials: Client ID and Client Secret for authentication.
Troubleshooting
- Ensure Client ID and Client Secret are correctly provided; missing credentials will cause authentication errors.
- Verify the 'end_to_end' identifier is correct and exists in the Zendry system to avoid empty or error responses.
- If using a custom endpoint, ensure the endpoint URL and HTTP method are correctly set.
- For non-GET requests, ensure the JSON body is valid; invalid JSON will cause request failures.
Links
- Zendry API Documentation - Official documentation for Zendry API endpoints and usage.