LEDGERS icon

LEDGERS

Interact with LEDGERS API
Join our community

Actions34

Overview

This node interacts with the "Purchase Operation (India)" resource of the LEDGERS API, specifically supporting the "View Voucher" operation. It retrieves detailed information about a purchase voucher, purchase invoice, or purchase order by its unique ID. This is useful for workflows that need to fetch and process purchase-related documents for accounting, auditing, or reporting purposes.

Practical examples include:

  • Automatically retrieving purchase voucher details after creation for validation or further processing.
  • Fetching purchase invoice data to integrate with other financial systems.
  • Accessing purchase order information to verify order status or details within an automated workflow.

Properties

Name Meaning
ID The unique identifier of the purchase invoice, voucher, or purchase order to retrieve. This is a required string input.

Output

The node outputs JSON data representing the full details of the requested purchase voucher (or invoice/order). The exact structure depends on the API response but typically includes fields such as voucher metadata, line items, amounts, dates, vendor details, and status.

No binary data output is indicated in the source code.

Dependencies

  • Requires an API key credential and user authentication credentials (email and password) for the LEDGERS API.
  • The node performs a login request to obtain an API token before making subsequent requests.
  • The base URL for the API is configurable via credentials.
  • Uses HTTP requests to interact with the LEDGERS API endpoints.

Troubleshooting

  • Authentication failures: If the node returns errors related to authentication, verify that the provided API key, email, and password are correct and have sufficient permissions.
  • Invalid or missing ID: Ensure the "ID" property is correctly set and corresponds to an existing purchase voucher/invoice/order.
  • API endpoint issues: Network problems or incorrect API URLs can cause request failures; check connectivity and credential configuration.
  • Unexpected API responses: If the API changes or returns unexpected data structures, the node may fail or return incomplete data.

Links and References

Discussion