Skip to content

[DEPR]: Contentstore and enrollment API versions superseded by FC-0118 #39128

Open

Description

@Faraz32123

RFC Start Date

N/A -- Already Accepted

Target Plan Accepted Date

N/A -- Already Accepted

Target Transition Unblocked Date

Immediately -- Transition Already Unblocked

Earliest Breaking Changes Unblocked Date

One named release after the release this deprecation ships in

Rationale

As part of FC-0118 (API standardization), a set of Studio contentstore
endpoints and the LMS enrollment API were re-issued at new versions rather than
changed in place. The standardization ADRs mandate changes that are breaking for
existing consumers:

  • ADR 0029 replaces the legacy {"developer_message": ..., "error_code": ...}
    error shape with an RFC 7807 envelope (type, title, status, detail,
    instance). Any client parsing error responses would break.
  • ADR 0028 moves from APIView to ViewSet + DefaultRouter, changing URL
    patterns (trailing slashes, router-managed routing).
  • ADR 0026 standardizes authentication and removes the deprecated
    BearerAuthentication, so Bearer-only consumers lose access.
  • ADR 0032 standardizes pagination, changing the response envelope on list
    endpoints.

Issuing new versions let existing consumers migrate on their own timeline
instead of absorbing a silent breaking change. That migration window is what
this ticket closes: the old versions are now redundant, and keeping both means
every future change to these endpoints has to be made twice.

Description

All replacements are merged and available today via
#38755.

Deprecated endpoint Replacement Standardization issue
GET/POST /api/contentstore/v0/xblock/{course_id} and /{course_id}/{usage_key} GET/POST/PATCH/DELETE /api/contentstore/v1/xblock/{usage_key}/ #38368
/api/enrollment/v1/ — enrollment, enrollments, course/{course_id}, unenroll/, roles/, enrollment_allowed/ /api/enrollment/v2/ #38369
GET/PUT /api/contentstore/v1/course_details/{course_id} GET/PUT /api/contentstore/v3/course_details/{course_key}/ #38370
GET /api/contentstore/v1/home GET /api/contentstore/v3/home/ #38371
GET /api/contentstore/v2/home/courses GET /api/contentstore/v4/home/ #38372
POST /api/contentstore/v0/grading/{course_id} PATCH /api/contentstore/v3/authoring_grading/{course_key}/ #38373

Consumers migrating should expect the RFC 7807 error envelope, router-managed
URLs (note the trailing slash), JWT or session auth in place of Bearer, and on
list endpoints the standardized pagination envelope.

Deprecation Schedule

The old versions are deprecated as of this ticket and will be removed one
named release after
the release in which this deprecation ships, giving
operators and plugin authors a full release cycle on a supported version.

  1. Now — endpoints marked deprecated: deprecated: true in the OpenAPI
    schema, a Warning response header, and docs pointing at the replacements.
  2. Next named release — both versions ship; the deprecated ones still work.
  3. The release after — old versions removed.

Task List

This ticket is the umbrella for API deprecations arising from the FC-0118
standardization work. Further areas will be appended as their replacement
versions merge:

  • contentstore xblock, course_details, home (v1 and v2), grading; LMS enrollment v1 — #38755

Activity

  1. added
    deprProposal for deprecation & removal per OEP-21
    on Sep 18, 2026
  2. Abdul-Muqadim-Arbisoft commented on Sep 27, 2026

    @Abdul-Muqadim-Arbisoft
    Contributor

    Entry for this ticket: contentstore video uploads. The replacement is in review in #39102; please add the lines below when it merges.

    Rows for the Description table:

    Deprecated endpoint Replacement Standardization issue
    POST /api/contentstore/v0/videos/uploads/{course_id} POST /api/authoring/v1/courses/{course_key}/videos/ #39060
    GET/DELETE /api/contentstore/v0/videos/uploads/{course_id}/{edx_video_id} GET /api/authoring/v1/courses/{course_key}/videos/ (the listing the v0 GET returns) and GET/DELETE /api/authoring/v1/courses/{course_key}/videos/{edx_video_id}/ #39060

    Line for the Task List:

    How it is marked: deprecated: true in the published OpenAPI schema. The superseded views are left untouched: no response header and no deprecation notes in code.

    The timeline is this ticket's: removed one named release after the release this ships in.

  3. Abdul-Muqadim-Arbisoft commented on Oct 4, 2026

    @Abdul-Muqadim-Arbisoft
    Contributor

    Entry for this ticket: contentstore video management. The replacement is in review in #39186; please add the lines below when it merges.

    Rows for the Description table:

    Deprecated endpoint Replacement Standardization issue
    GET /api/contentstore/v1/videos/{course_id}/{edx_video_id}/usage GET /api/authoring/v2/courses/{course_key}/video_usages/{edx_video_id}/ #39071
    PUT /api/contentstore/v1/videos/{course_id}/download POST /api/authoring/v2/courses/{course_key}/video_archives/ #39071

    Line for the Task List:

    Removal step for this area: move VideoDownloadThrottle out of cms/djangoapps/contentstore/rest_api/v1/views/videos.py before that module is deleted. The v2 archive view and its tests import it from there, so deleting the module first breaks the import of cms/urls.py.

    How it is marked: deprecated: true in the published OpenAPI schema. The superseded views are left untouched: no response header and no deprecation notes in code.

    The timeline is this ticket's: removed one named release after the release this ships in.

  4. taimoor-ahmed-1 commented on Oct 13, 2026

    @taimoor-ahmed-1
    Contributor

    Entry for this ticket: contentstore course grading. The replacement is in review in #39227; please add the lines below when it merges.

    Rows for the Description table:

    Deprecated endpoint Replacement Standardization issue
    GET/POST /api/contentstore/v1/course_grading/{course_id} GET/PATCH /api/authoring/v3/courses/{course_key}/grading/ #39065
    GET/PATCH /api/contentstore/v3/authoring_grading/{course_key}/ GET/PATCH /api/authoring/v3/courses/{course_key}/grading/ #39065

    The existing POST /api/contentstore/v0/grading/{course_id} row should point at the same replacement, PATCH /api/authoring/v3/courses/{course_key}/grading/. #39227 also marks that v0 route deprecated in the CMS schema, which it was not until now.

    Line for the Task List:

    Migration notes

    • The GET returns the grading policy at the top level instead of under course_details.
    • ?view=full adds course_assignment_lists, default_grade_designations, is_credit_course, show_credit_eligibility and mfe_proctored_exam_settings_url, under the v1 names. grace_period also gains seconds.
    • The v1 POST body is accepted unchanged by PATCH. PATCH also accepts partial bodies, changing only the fields sent.
    • Bearer tokens are not accepted: use JWT or a session.
    • Errors use the standardized envelope.
    • The trailing slash is required.
    • Slash-form (Old Mongo) course keys are served only by the deprecated addresses.

    How it is marked: deprecated: true in the CMS schema, plus a docstring note on the v1 and v0 views. No response header.

    Window: this ticket's own schedule. The marking ships in the next named release after Verawood, and the deprecated addresses are removed one named release after that.

  5. taimoor-ahmed-1 commented on Oct 14, 2026

    @taimoor-ahmed-1
    Contributor

    Entry for this ticket: contentstore course index. The replacement is in review in #39229; please add the lines below when it merges.

    Rows for the Description table:

    Deprecated endpoint Replacement Standardization issue
    GET /api/contentstore/v1/course_index/{course_id} GET /api/authoring/v2/courses/{course_key}/outline/?view=full (the screen payload) or the default thin outline tree #39066

    Line for the Task List:

    Migration notes

    • ?view=full keeps v1's top-level keys and per-node shape, minus initial_user_clipboard. Read the clipboard from /api/content-staging/v1/clipboard/.
    • The default view is a thin tree two levels deep. Nodes cut at the depth limit carry children_url.
    • ?format=concise has no equivalent; v1's concise form also listed the components inside units.
    • Blocks with pre-1900 start dates are reported as stored; v1 repaired them on read.
    • Inactive browser sessions and Bearer tokens are refused; use JWT or an active session.
    • Slash-form course keys are served only by v1.
    • The trailing slash is required.
    • Errors use the standardized envelope.

    How it is marked: deprecated: true in the CMS schema, plus a docstring note on the v1 view. No response header.

    Window: this ticket's own schedule. The marking ships in the next named release after Verawood, and the deprecated address is removed one named release after that.

  6. Abdul-Muqadim-Arbisoft commented on Oct 15, 2026

    @Abdul-Muqadim-Arbisoft
    Contributor

    Entry for this ticket: user API directory listings (users, user preferences, time zones). The replacement is in review in #39237; please add the lines below when it merges.

    Rows for the Description table:

    Deprecated endpoint Replacement Standardization issue
    GET /api/user/v1/users/ GET /api/user/v2/users/ #39058
    GET /api/user/v1/users/{id}/ GET /api/user/v2/users/{username}/ #39058
    GET /api/user/v1/user_prefs/ GET /api/user/v2/user_preferences/ #39058
    GET /api/user/v1/user_prefs/{id}/ GET /api/user/v2/user_preferences/{username},{key}/ #39058
    GET /api/user/v1/preferences/{pref_key}/users/ GET /api/user/v2/users/?preference_key={pref_key} #39058
    GET /api/user/v1/forum_roles/{name}/users/ GET /api/user/v2/users/?forum_role={name}&course_key={course_key} #39058
    GET /api/user/v1/preferences/time_zones/ GET /api/user/v2/time_zones/ #39058

    Line for the Task List:

    • user API directory listings (users, user preferences, time zones) — #39237 (#39058)

    How it is marked: deprecated: true in the published OpenAPI schema. The superseded views are left untouched: no response header and no deprecation notes in code.

    The timeline is this ticket's: removed one named release after the release this ships in.

  7. Faraz32123 commented on Oct 15, 2026

    @Faraz32123
    ContributorAuthor

    Entry for this ticket: contentstore legacy library list. The replacement is in review in #39238; please add the lines below when it merges.

    Rows for the Description table:

    Deprecated endpoint Replacement Standardization issue
    GET /api/contentstore/v1/home/libraries GET /api/authoring/v4/legacy_libraries/ #39069
    GET /api/contentstore/v3/home/libraries/ GET /api/authoring/v4/legacy_libraries/ #39069
    GET /api/authoring/v3/home/libraries/ GET /api/authoring/v4/legacy_libraries/ #39069

    Line for the Task List:

    How it is marked: deprecated: true in the published CMS OpenAPI schema (/api/contentstore/v3/home/libraries/ already carried it under the v3 home prefix; the v1 path and /api/authoring/v3/home/libraries/ gain it here). The superseded views are left untouched: no response header and no deprecation notes in code.

    The timeline is this ticket's: removed one named release after the release this ships in.

    Before removal: on sites with ENABLE_CREATOR_GROUP, the v1 and v3 lists create the unrequested CourseCreator record on GET, and POST /request_course_creator depends on that record. The v4 list does not create it; the Studio home and course rerun contexts still do. Removing these addresses is safe for that flow only while one of those remains, and #39068 (Studio home) must provide an explicit write before it drops the other. Details in #39238, "Deprecations".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    deprProposal for deprecation & removal per OEP-21

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions