Google Classroom API
Browse all Google APIs39
AI ReadinessNon-Ready (F)39/100
Official vendor OpenAPI document · agent-readyEducationLmsoauth295 EndpointsREST
For Agents
Manage Google Classroom courses, rosters, coursework, announcements, and submissions across teacher and student flows.
Use for: Create a new Google Classroom course, List all students in a Classroom course, Post an announcement to a Classroom course, Create a Classroom assignment with a due date
Not supported: Does not host video meetings, manage Workspace user accounts, or store attachment file contents - use for Google Classroom course, roster, coursework, and submission operations only.
The Google Classroom API gives schools, education-tech vendors, and content publishers programmatic access to courses, rosters, coursework, announcements, submissions, grades, and add-on attachments inside Google Classroom. It supports both teacher and student perspectives via OAuth, manages course aliases for SIS sync, and exposes coursework state transitions including turn-in, return, and reclaim. It is the backbone for SIS-Classroom integrations and add-ons that embed inside the Classroom stream.
Install Jentic One Beta
Connect the Google Classroom API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google Classroom API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fclassroom" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fclassroom" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Google Classroom API.
Create and update Classroom courses and manage course aliases for SIS sync
Enroll, list, and remove students and teachers in a course
Post announcements and coursework with attached materials and due dates
Read and grade student submissions and return assignments to students
Manage add-on attachments that surface third-party content inside the Classroom stream
List, mark, and reclaim coursework on behalf of students
Use Cases
Patterns agents use Google Classroom API for, with concrete tasks.
★ SIS-to-Classroom Roster Sync
School districts sync rosters from a Student Information System into Google Classroom by creating courses with stable course aliases and reconciling student and teacher membership nightly. The aliases endpoints let the SIS use its own ids while keeping Classroom in sync. Most integrations use a service account with domain-wide delegation to act on behalf of teachers.
Create a course with id stub via POST /v1/courses, then POST /v1/courses/{courseId}/aliases with alias=d:district_id_12345 and add a teacher via /v1/courses/{courseId}/teachers.
Curriculum Publishing
Education-tech vendors push pre-built lessons, quizzes, and reading assignments into a teacher's Classroom course as coursework with attached Drive resources or YouTube links. The API supports scheduled publication and per-student materials. This eliminates teachers re-creating content manually each term.
POST /v1/courses/{courseId}/courseWork with title="Week 3 Reading", workType=ASSIGNMENT, dueDate, and a Drive attachment.
Grading and Feedback Loops
Schools build grading dashboards that read student submissions, set assigned grades, and return work to students at scale. The submissions endpoints expose state transitions (TURNED_IN, RETURNED, RECLAIMED) and allow updates to draftGrade and assignedGrade with patch masks. Teachers see results immediately in their Classroom UI.
PATCH /v1/courses/{courseId}/courseWork/{courseWorkId}/studentSubmissions/{id} with assignedGrade=85 then POST :return.
AI Agent Teaching Assistant via Jentic
An AI agent through Jentic acts as a teaching assistant - listing pending submissions, suggesting feedback drafts for the teacher to review, posting announcements, and creating follow-up assignments. Jentic isolates the Workspace OAuth credentials so the agent never holds the teacher's refresh token directly.
Through Jentic, search classroom_courses_announcements_create, load schema, and execute it for course 12345 with text "Reminder: project due Friday".
Key Endpoints
95 endpoints — the google classroom api gives schools, education-tech vendors, and content publishers programmatic access to courses, rosters, coursework, announcements, submissions, grades, and add-on attachments inside google classroom.
METHOD
PATH
DESCRIPTION
POST
/v1/courses
Create a Classroom course
GET
/v1/courses
List courses for the caller
POST
/v1/courses/{courseId}/aliases
Create an external alias for a course
POST
/v1/courses/{courseId}/announcements
Post an announcement to a course
POST
/v1/courses/{courseId}/courseWork
Create coursework (assignment, material, or question)
GET
/v1/courses/{courseId}/announcements
List announcements in a course
POST
/v1/courses
Create a Classroom course
GET
/v1/courses
List courses for the caller
POST
/v1/courses/{courseId}/aliases
Create an external alias for a course
POST
/v1/courses/{courseId}/announcements
Post an announcement to a course
POST
/v1/courses/{courseId}/courseWork
Create coursework (assignment, material, or question)
GET
/v1/courses/{courseId}/announcements
List announcements in a course
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
G
Google Classroom API
- Non-Ready (F)39/100
70
Foundational Compliance56
Developer Experience & Jentic Compatibility16
AI-Readiness & Agent Experience86
Agent Usability63
Security65
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
70
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: B+Signals: 4
78%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
16
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
66%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
86
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: ASignals: 1
86%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
65
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
65%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Google Classroom API by hand means standing up Workspace OAuth or a service account across the classroom scopes, refreshing scoped access tokens, and sequencing course, roster, coursework, and submission calls yourself. Through Jentic you install once, import the Google Classroom API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
The API puts the course in the URL path (/v1/courses/{courseId}/courseWork, /v1/courses/{courseId}/announcements), so a rule can pin your agent to one course: it can post announcements and coursework there and nowhere else. You choose the operations it may call, so ones like managing aliases are not included unless you add them.
Credential isolation
Your Workspace OAuth credentials or service account key with classroom scopes are stored once, encrypted, by your own Jentic One instance and injected at execution time. The agent receives only short-lived access tokens and the refresh token and service account JSON never enter its prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a Classroom assignment', and Jentic returns the courses courseWork create operation with its parameter schema, including workType and submissionModificationMode enums, so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Google Classroom API through Jentic.
What authentication does the Google Classroom API use?
It uses OAuth 2.0 with one or more classroom.* scopes, scoped per resource (courses, rosters, coursework, announcements). Service accounts with domain-wide delegation are common for SIS sync. Through Jentic, the credential is stored encrypted in your Jentic One instance and the agent receives only short-lived scoped access tokens.
Can I create a Classroom course via the API?
Yes. POST /v1/courses with name, ownerId, and optionally description and section. Add a stable external id by POSTing /v1/courses/{courseId}/aliases with an alias starting with d: for domain-scoped aliases or p: for project-scoped aliases.
What are the rate limits for the Google Classroom API?
Google enforces per-project quotas (typically thousands of read requests per minute and hundreds of writes) and per-user limits to prevent abuse. Coursework creation and submission patch operations sit under the lower per-user quota, so batch where possible and back off on 429.
How do I post an announcement through Jentic?
Use the Jentic search query "post announcement to Google Classroom" to discover the courses.announcements.create operation, load its schema, and execute it with the courseId and the text body. Run pip install jentic to get started.
Can the API grade and return assignments?
Yes. PATCH a studentSubmission with assignedGrade and an updateMask, then POST :return on the submission to push the grade and feedback back to the student. The student sees the result in the Classroom UI immediately.
Is the Google Classroom API free?
It is free for Google Workspace for Education customers. There is no per-call charge from Google, though some scopes require admin approval before they can be used by third-party apps.
Can I limit what my agent is allowed to do with the Google Classroom API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which Classroom operations and credentials your agent may use. Since the API puts the course in the URL path, such as /v1/courses/{courseId}/announcements and /v1/courses/{courseId}/courseWork, a rule can pin your agent to a single course so it can post announcements and coursework there and nowhere else. You also pick the exact operations it may call, so higher-risk ones like managing course aliases stay out of reach unless you explicitly add them.
GET STARTED