Actions45
- General Actions
- About API Actions
- Accounts API Actions
- Transactions API Actions
- Categories API Actions
- Tags API Actions
- Rules & Groups API Actions
Overview
The "List Accounts" operation of the FireFly III node retrieves a list of financial accounts from the FireFly III API. This includes asset, cash, expense, and revenue accounts, among others. Users can filter accounts by type and paginate through results.
This operation is useful for scenarios such as:
- Displaying all user accounts in a dashboard or report.
- Synchronizing account lists with other financial tools.
- Filtering accounts by type to focus on specific categories like assets or expenses.
Example use case: A user wants to fetch all their asset accounts to analyze their investment portfolio separately from their daily expenses.
Properties
Name | Meaning |
---|---|
X-Trace-ID | A unique UUID identifier for the request, used for debugging and tracing (e.g., 123e4567-e89b-12d3-a456-426614174000 ). |
Account Type | Filter accounts by type. Options include: -- (no filter), All , Asset , Cash , Expense , Revenue . |
Pagination Options | Collection of pagination settings: - Limit: Max number of results to return (minimum 1, default 50). - Page: The page number to retrieve (minimum 1, default 1). |
Account Balance Date | Collection containing: - Date: A date string formatted as YYYY-MM-DD to show the account's balance on that day. |
Output
The output is a JSON object representing the list of accounts returned by the FireFly III API. It typically contains an array of account objects with details such as account ID, name, type, and balances.
No binary data is output by this operation.
Example structure (simplified):
{
"data": [
{
"id": "1",
"name": "Checking Account",
"type": "asset",
"balance": 1000.00,
...
},
{
"id": "2",
"name": "Credit Card",
"type": "expense",
"balance": -500.00,
...
}
],
"meta": {
"pagination": {
"total": 10,
"count": 2,
"per_page": 50,
"current_page": 1,
"total_pages": 1
}
}
}
Dependencies
- Requires an authenticated connection to the FireFly III API using an OAuth2 or similar API key credential.
- The node depends on the FireFly III API being accessible and properly configured.
- No additional external services are required beyond the FireFly III API.
Troubleshooting
- Empty or missing results: Ensure the correct account type filter is set or try removing the filter to get all accounts.
- Pagination issues: If not all accounts appear, check the
Limit
andPage
parameters to navigate through pages correctly. - Invalid X-Trace-ID: The trace ID should be a valid UUID if provided; otherwise, omit it.
- API authentication errors: Verify that the API credentials are valid and have sufficient permissions.
- Date format errors: When using the Account Balance Date, ensure the date is in
YYYY-MM-DD
format to avoid API errors.
Common error messages may relate to invalid parameters or authentication failures. Reviewing the API documentation linked below can help resolve these.