EG MainManager is automatable through its API

EG MainManager is automatable today through MainManager API v3. The API page, updated 5 June 2026, describes a REST API under /api/v3/ for assets, building components, incidents, work orders, tasks, documents, and messages. Each listed resource supports list, fetch by ID, create, and update, plus bulk writes, pageSize and pageNumber pagination, and dateModified incremental sync. A token is requested with POST /restapi/token using grant_type=password, a username, and a password. The example response returns access_token, refresh_token, token_type Bearer, and expires_in 3600. Later calls send Authorization Bearer. The paths are relative to the customer's MainManager web path. Login documentation says a user needs a username, password, and a web path to a MainManager database. The opened product page leaves hosting unstated, so this record classifies the product as web. Calls run as the authenticated user and follow that user's module rights. The same page says more resources are still to come, so coverage is partial. The Facility app is downloaded from the App Store or Google Play and needs the database app key. A separate note says Danish municipalities can sync organisation and employees from KOMBIT and use KOMBIT single sign-on. MCP, Zapier, Make, Power Automate, n8n, and computer-use viability are unassessed. The API scores 7 because the documented surface is broad and current. The password grant, per-user module rights, and the unfinished resource list keep the score at 7.

Best path today: api · Overall automatability: 7/10