REST API Support for Automation and Integration

In 2026, modern enterprise tooling is expected to provide a REST API to enable automation, integration, and platform-independent workflows. Currently, the product relies on a Windows-based PowerShell module that requires installing an agent, which limits flexibility and prevents organizations from adopting modern, scalable automation practices.

A REST API would allow seamless integration with various platforms without dependency on Windows, agents, or scheduled tasks. It would enable organizations to build robust automation scenarios using tools and platforms of their choice.

Example Integrations

A REST API would unlock the ability to integrate with systems such as TOPdesk or ControlUp Workflows. For example:

Based on an attribute on an asset card in TOPdesk, an automated action could add a device to the correct device collection that represents the DTAP stage (Development, Test, Acceptance and Production). This is currently not possible in a modern and platform-agnostic way. Today, it requires a scheduled task on a server with the workspace agent installed, a cumbersome and outdated approach.

Expected Capabilities

A modern REST API should ideally support:

• Querying and managing users, devices, collections, packages, licensing, servers

• Managing configuration and context assignments

• Secure authentication (OAuth2 / modern token-based auth)

• Integration-friendly, well-documented endpoints

Conclusion

Introducing a REST API would bring the platform in line with modern standards, remove unnecessary dependencies, and enable powerful, flexible automation scenarios used in today’s enterprise environments. This would significantly improve usability, integration potential, and long-term scalability.