Classroom API overview

Third-party developers and administrators can use the Classroom API. Teachers and students can authorise third-party applications.

Using the Classroom API, you can do programmatically many of the things that teachers and students can do through the Classroom UI. For example, you can synchronise with student information systems, view all the classes being taught in a domain and manage coursework.

Non-Google services can use the Classroom API to integrate features with Classroom. For example, an app might let a teacher copy and reuse a Classroom class, instead of re-creating the class and re-adding each student. Applications can also programmatically view, create and modify Classroom work, add materials to work, hand in work for students and send marks back to Classroom.

Before an app or service can access Classroom data, the app must request authorisation from the Classroom user. The app asks for the specific permissions it needs (such as a username, email address or profile photo), and the user can approve or reject the service’s request. To authorise permission, the Classroom API uses a common Internet standard called OAuth.

For Google Workspace for Education administrators

As a Google Workspace for Education administrator, you control how data in a domain is shared. In the Google Admin console, you can specify whether teachers and students in your domain can authorise services to access their Classroom data. You can configure access by organisational unit. Learn how to set Classroom data access.

In the Admin console, you can also view the services that have been granted access to a user's account in your domain, and you can revoke authorisations if needed.

The specific tasks that the Classroom API can perform depends on what role a user has in a class. Just like in the Classroom UI, a user can be a student, teacher or administrator. Teachers and students can approve third-party applications and report abuse.