Expand RMM API Access for Full Endpoint Interaction
Expand the RMM API to allow full interaction with all relevant endpoints, enabling deeper automation and integration with Neo. This would unlock the ability to programmatically manage devices, alerts, maintenance, and asset metadata without manual intervention.
Use Cases:
Updating Custom Fields
Read and update device custom fields via API
Bulk updates across multiple devices
Enables dynamic data syncing between systems
Maintenance Scheduling
Programmatically schedule maintenance windows for devices or groups
Modify or cancel existing maintenance events
Supports automated patching workflows and change management processes
Alert / Condition Management
Reset or clear alerts/conditions via API
Trigger remediation workflows externally
Improve alert lifecycle automation and reduce technician intervention
Asset Tagging
Add, remove, and query asset/device tags
Enable dynamic grouping and policy assignment
Improve reporting, filtering, and automation targeting
Device Approvals
Approve or reject newly discovered / pending devices via API
Query approval status for devices
Support automated onboarding workflows based on predefined rules
Reduce manual review steps for trusted device deployments
Enable tighter integration between Neo-driven workflows and RMM enrollment processes
Log in to comment and vote
Comments2
Ryan
Oct 6
Neo agents can now use the full NinjaOne and Datto RMM APIs. They can read and update device custom fields, set maintenance windows and clear alerts. Turn this on in the agent's tool permissions.
John Stavrakos
Jun 8
Symmetric IT Group