openedx / openedx/openedx-platform
[API] Course Grading
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 4.4k
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 42
Description
Functional Area: Course Grading
Endpoints under this functional area:
| Module | API Version | Resource / Endpoint | HTTP Method | Description |
|---|---|---|---|---|
| Course Grading | v1 | /contentstore/v1/course_grading/{course_id} |
GET | Retrieves course grading configuration for a specific course ID. Returns JSON including graders (types, weights, minimum and drop counts), grade cutoffs, grace periods, minimum grade credit, course assignment lists, default grade designations, credit eligibility, and proctored exam settings URL. Path parameter course_id is required. Supports AI tools or external systems in calculating grades, monitoring credit eligibility, or integrating grading rules into analytics pipelines. |
| Course Grading | v1 | /contentstore/v1/course_grading/{course_id} |
POST | Updates the grading configuration for a given course. Accepts JSON body with graders, grade cutoffs, grace periods, minimum grade credit, and credit course flag. Returns updated grading configuration. Path parameter course_id is required. Useful for AI or external tools automating course grading rules, bulk updates, or synchronizing grading policies across multiple courses. |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the implementation and API tests for /contentstore/v1/course_grading/{course_id}. Compare the GET and POST behavior with the listed request and response details, then confirm what change is expected because the issue does not define acceptance criteria or identify files. Done should mean the requested course-grading API behavior is implemented and verified by tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100