Patch add-on attachment for course work

documented

Updates an add-on attachment for course work.

POST /v1/courses/{courseId}/courseWork/{itemId}/addOnAttachments/{attachmentId}:patchCoursesno implementation yet0 runs

Input

course_id

Course ID

COURSE_ID

item_id

Course Work Item ID

ITEM_ID

attachment_id*

Attachment ID

ATTACH_ID

post_id*

Post ID

POST_ID

update_mask*

Update Mask

title,dueDate,dueTime,maxPoints

title*

Attachment Title

Reading Materials

teacherViewUri

Teacher View URI

https://teacher.example/view?id=...

studentViewUri

Student View URI

https://student.example/view?id=...

studentWorkReviewUri

Student Work Review URI

https://review.example/view?id=...

year

Due Date Year

2026

month

Due Date Month

day

Due Date Day

hours

Due Time Hours

minutes

Due Time Minutes

maxPoints

Max Points

100

Calls Google Classroom as you (your API key is your account); keychains.dev holds the credentials.

Call it from anywhere

curl -X POST https://open-integrations.dev/api/run/google-classroom/course-work-add-on-attachments-patch-post-v1-courses-courseid-coursework-itemid-addonattachments-attachmentid-patch \
  -H "Authorization: Bearer $ANTHROPIC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"input": {}}'

Any Anthropic key works. It is never stored, and only spent when a snippet has to be written. API docs.

Credentials

This action calls Google Classroom on your behalf. Your tokens live in keychains.dev, never here. Get an API key at classroom.google.com.

Documented only

The endpoint and inputs are known, but nobody has written the snippet yet. Running it has Claude implement and test it live using your own AI tokens, in about a minute, and the result becomes version one for everyone. Prefer to write it yourself? Open a pull request.