Rest Accounting

Interact with Rest Accounting API

Actions13

Overview

This node integrates with the Rest Accounting API to perform various accounting-related operations. Specifically, for the Journal Entries - Search operation, it allows users to query journal entries based on multiple filter criteria such as date range, reference, and description. This is useful for retrieving specific journal entries from an accounting system for review, reporting, or further processing.

Practical examples include:

  • Searching for all journal entries within a particular month.
  • Filtering journal entries by a specific reference code or description keyword.
  • Paginating through large sets of journal entries to process them in batches.

Properties

Name Meaning
Query Parameters A collection of filters and pagination options to refine the search results:
- Start Date The start date (inclusive) to filter journal entries by their date.
- End Date The end date (inclusive) to filter journal entries by their date.
- Reference Filter journal entries by a specific reference string.
- Description Filter journal entries by matching description text.
- Page The page number of results to retrieve (for pagination).
- Page Size The number of journal entries to return per page.

Output

The output is an array containing one item per input, each with a json property holding the response data from the API call. For the Journal Entries Search operation, the json field contains the list of journal entries matching the query parameters, typically including details like entry dates, references, descriptions, amounts, and other relevant fields returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Rest Accounting API.
  • The node expects the base URL of the Rest Accounting API and the API key to be configured in the credentials.
  • Uses HTTP requests with JSON payloads and query parameters to interact with the API.

Troubleshooting

  • Common issues:
    • Invalid or missing API key credential will cause authentication failures.
    • Incorrect date formats in the "Start Date" or "End Date" fields may result in API errors or empty results.
    • Requesting pages beyond the available data set may return empty arrays.
  • Error messages:
    • "Request failed" indicates a network or API error; check API availability and credentials.
    • Errors with messages related to invalid parameters suggest verifying the input values, especially date strings and pagination numbers.

Links and References

Discussion