Rest Accounting

Interact with Rest Accounting API
Join our community

Actions13

Overview

This node integrates with a RESTful Accounting API to manage accounting data programmatically. Specifically, the Accounts - Update operation allows users to modify existing account records by specifying the account ID and the fields to update.

Typical use cases include:

  • Updating account details such as code, name, type, or parent account in an automated workflow.
  • Synchronizing account information from other systems or databases.
  • Correcting or enhancing account metadata without manual intervention.

For example, you might update an account's name and type after receiving updated financial data from an external source.

Properties

Name Meaning
Account ID The unique numeric identifier of the account to update.
Account Fields A collection of fields to update on the account. Possible fields:
- Code: The account code (string).
- Name: The account name (string).
- Type: The account type (string).
- Parent ID: The numeric ID of the parent account (number).

Output

The output is a JSON object representing the updated account record as returned by the REST Accounting API. This typically includes all current properties of the account after the update has been applied.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": 123,
  "code": "4000",
  "name": "Sales Revenue",
  "type": "Revenue",
  "parent_id": 10,
  "created_at": "2023-01-01T12:00:00Z",
  "updated_at": "2024-06-01T15:30:00Z"
}

Dependencies

  • Requires an API key credential for authenticating requests to the REST Accounting API.
  • The base URL of the API must be configured in the credentials.
  • The node uses HTTP methods (PUT) to send updates to the /accounts/{accountId} endpoint.

Troubleshooting

  • Common issues:

    • Invalid or missing API key: The request will fail authentication.
    • Nonexistent Account ID: Trying to update an account that does not exist will result in an error.
    • Invalid field values: Providing incorrect data types or invalid values in Account Fields may cause the API to reject the request.

  • Error messages:

    • "Request failed": Generic failure, often due to network issues or invalid API responses.
    • API-specific errors returned in the response body should be reviewed for details (e.g., "Account not found", "Invalid field value").

  • Resolutions:

    • Verify API key and base URL configuration.
    • Confirm the Account ID exists before attempting an update.
    • Validate input fields conform to expected formats and constraints.

Links and References

Discussion