Actions83
- Bills Actions
- Alerts Actions
- Alert Rules Actions
- ARP Actions
- Devices Actions
- Device Groups Actions
- Inventory Actions
- Locations Actions
- Logs Actions
- Poller Groups Actions
- Ports Actions
- Port Groups Actions
- Routing Actions
- Services Actions
- Switching Actions
Overview
The node integrates with the LibreNMS network monitoring system, specifically providing access to billing information under the "Bills" resource. The "Get by Reference" operation allows users to retrieve detailed billing data for a specific bill identified by its unique reference identifier. This is useful in scenarios where you need to fetch billing details programmatically based on a known bill reference, such as automating invoice retrieval, auditing billing records, or integrating billing data into other financial systems.
For example, a user can input a bill reference ID and optionally specify the billing period (current or previous) to get the corresponding bill details from LibreNMS.
Properties
| Name | Meaning |
|---|---|
| Bill Reference | The unique identifier of the bill to retrieve. |
| Options | Additional options for the request: |
| Period | Billing period to retrieve. Possible values: "Current" (default) or "Previous". |
Output
The output JSON contains the detailed billing information corresponding to the specified bill reference. This typically includes fields such as bill amounts, dates, usage details, and other relevant billing metadata as provided by LibreNMS.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential to authenticate with the LibreNMS API.
- The node expects the base URL of the LibreNMS instance to be configured in the credentials.
- Optionally supports skipping SSL certificate validation based on credential settings.
Troubleshooting
Common issues:
- Invalid or missing bill reference will result in errors or empty responses.
- Incorrect API credentials or URL misconfiguration may cause authentication failures.
- Specifying an unsupported billing period value could lead to unexpected results or errors.
Error messages:
- Authentication errors usually indicate invalid API keys or incorrect endpoint URLs.
- "Bill not found" or similar messages suggest the provided bill reference does not exist.
Resolutions:
- Verify the bill reference string is correct and exists in LibreNMS.
- Check API credentials and ensure the LibreNMS URL is reachable and correctly set.
- Use only supported period options ("Current" or "Previous").
Links and References
(Note: The above link is a general reference to LibreNMS API docs for further details.)