Google Classroom Python API Docs | dltHub

Build a Google Classroom-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Google Classroom is a RESTful API used to manage classes, rosters, course work, announcements, and user profiles in Google Classroom. The REST API base URL is https://classroom.googleapis.com and all requests require an OAuth 2.0 Bearer token in the Authorization header.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Google Classroom data in under 10 minutes.


What data can I load from Google Classroom?

Here are some of the endpoints you can load from Google Classroom:

ResourceEndpointMethodData selectorDescription
coursesv1/coursesGETcoursesReturns a list of courses
course_workv1/courses/{courseId}/courseWorkGETcourseWorkReturns a list of coursework
course_work_materialsv1/courses/{courseId}/courseWorkMaterialsGETcourseWorkMaterialReturns a list of coursework materials
student_submissionsv1/courses/{courseId}/courseWork/{courseWorkId}/studentSubmissionsGETstudentSubmissionsReturns a list of student submissions
teachersv1/courses/{courseId}/teachersGETteachersReturns a list of teachers in a course

How do I authenticate with the Google Classroom API?

Requests must include an Authorization header with a Bearer token containing a valid OAuth 2.0 access token.

1. Get your credentials

  1. Navigate to the Google Cloud Console (console.cloud.google.com). 2. Ensure your project is selected. 3. Navigate to APIs & Services > Credentials. 4. To access user data, click Create Credentials > OAuth client ID, select your application type (e.g., Desktop app or Web application), and follow the prompts to generate the client ID/secret. 5. Download the resulting JSON credentials file. 6. For simple public data, you can alternatively create an API key via Create Credentials > API key, though OAuth 2.0 is required for most Classroom API methods.

2. Add them to .dlt/secrets.toml

[sources.google_classroom_source] credentials = "REPLACE_ME"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Google Classroom API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python google_classroom_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline google_classroom_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset google_classroom_data The duckdb destination used duckdb:/google_classroom.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads v1.courses and v1.courses.courseWork from the Google Classroom API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def google_classroom_source(credentials=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://classroom.googleapis.com", "auth": {"type": "bearer", "token": credentials}, }, "resources": [ {"name": "courses", "endpoint": {"path": "v1/courses", "data_selector": "courses"}}, {"name": "course_work", "endpoint": {"path": "v1/courses/{courseId}/courseWork", "data_selector": "courseWork"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="google_classroom_pipeline", destination="duckdb", dataset_name="google_classroom_data", ) load_info = pipeline.run(google_classroom_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("google_classroom_pipeline").dataset() sessions_df = data.courses.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM google_classroom_data.courses LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("google_classroom_pipeline").dataset() data.courses.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Google Classroom data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Google Classroom?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines