I’m reaching out to highlight a challenge we’re facing with data retrieval in Atera and to request improvements that could streamline our workflows and enhance efficiency.

Currently, we rely on fields such as CustomerName, ScriptName, ScriptCategory, DeviceName, and others for managing processes and creating tickets. While the existing structure and tools are helpful, extracting and utilizing this data in a programmatic and scalable way can be cumbersome.

The Challenge:

The current methods require manual effort or complex workarounds to gather and process information from the above fields.
Automating workflows, such as linking data from scripts or devices directly into ticketing systems, is limited due to a lack of easily accessible API endpoints or consolidated data access methods.
Filtering and processing large datasets, such as script execution results or device statuses, are time-intensive and prone to errors.
Proposed Solution:
I’d like to request enhancements to the Atera platform, specifically:

Expanded API Functionality:

Endpoints that allow direct access to detailed data for fields like CustomerName, ScriptName, and ScriptCategory.
Support for advanced filtering and aggregation.
Unified Data Access:

A single method to retrieve device statuses, script execution details, and customer information in a unified response.
Streamlined Integration:

Easier methods to link retrieved data directly into tickets or other automated workflows.