Can AI agents automate Visma Flyt Skole?

Visma Flyt Skole is automatable today through its partner-gated External API, with OneRoster 1.2 as a second read-only roster path. The External API is a documented REST interface for employees, pupils, groups, access control, municipality metadata, and LMS export in PIFU, IMS, and ABC formats. Authorized clients can create and update employees and positions, update groups, and manage employee access groups. Change detection is pull-based for pupils, guardians, employees, groups, and memberships, not a documented push webhook. Authentication is OAuth 2.0 client credentials through Visma Connect. Visma Flyt provisions each application in the Visma Developer Portal, scopes it, and links municipal or school tenants in the Flyt Skole admin panel. Production access needs approval. A sandbox with a separate quota exists, and Visma states a 99.9 percent production SLA plus semantic versioning with at least six months of deprecated-version support. Default rate limits are per application; public numbers are not published. OneRoster 1.2 (Norwegian profile) exposes organizations, schools, courses, classes, users, enrollments, and academic sessions as JSON under a roster-core.readonly scope. Zapier, Make, Microsoft Power Automate, and n8n had no Flyt Skole connector in their public catalogs on 2026-08-21. No official SDK or general CLI was established. Vendor documentation does not settle first-party MCP ownership, and the official MCP registry had no Flyt Skole server. Computer-use viability is unassessed. Sibling Flyt products, including Barnehage, InSchool, and Voksenopplæring, are outside this record.

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