/
RA
rage
/
Main Frontend API
Search skmtc…
⌘K
Changes
Docs
Sign in
Sign in
APIs
5
Docs
History
Schema
Filter operations
certificates
6
chapters
6
chatbot-models
2
chatbots
5
code_giveaways
7
course_auditing
2
course_modules
7
course-credit-registrations
11
course-instances
15
course-plans
15
course-stats
28
course-students
9
courses
66
credit-registration-admin
34
credit-registrations
16
get
/api/v0/main-frontend/credit-registrations/my
GET `/api/v0/main-frontend/credit-registrations/my` - Every credit registration of the signed-in account, newest completion first.
get
/api/v0/main-frontend/credit-registrations/my/by-course-module/{course_module_id}
GET `/api/v0/main-frontend/credit-registrations/my/by-course-module/{course_module_id}` - The signed-in account's registration for one course module, or null when the pipeline has not created one yet.
put
/api/v0/main-frontend/credit-registrations/my/by-course-module/{course_module_id}/credit-justification
PUT `/api/v0/main-frontend/credit-registrations/my/by-course-module/{course_module_id}/credit-justification` - Records why the caller needs the credits in the study registry rather than a certificate. Advisory: nothing reads it, and it neither gates nor speeds up the registration the student goes on to make. Asked on the old registration page, so unlike the enrolment answers it is stored for completions on either path.
post
/api/v0/main-frontend/credit-registrations/my/by-course-module/{course_module_id}/enrolment-page-visit
POST `/api/v0/main-frontend/credit-registrations/my/by-course-module/{course_module_id}/enrolment-page-visit` - The caller opened the registration page after completing, and it is showing them how to enrol. Moves a waiting registration onto the schedule for students who have looked, or restarts that schedule at most once a day. Recorded against the completion too, so a visit before there is a registration, or before a student number is linked, still counts once there is; an unlinked caller's visit also makes the course code's enrolment list due sooner. Idempotent enough to call on every page load; the page sends it once per load.
get
/api/v0/main-frontend/credit-registrations/my/by-course-module/{course_module_id}/enrolment-route
GET `/api/v0/main-frontend/credit-registrations/my/by-course-module/{course_module_id}/enrolment-route` - What the caller said about where they enrol this module.
put
/api/v0/main-frontend/credit-registrations/my/by-course-module/{course_module_id}/enrolment-route
PUT `/api/v0/main-frontend/credit-registrations/my/by-course-module/{course_module_id}/enrolment-route` - Records which university relationship the caller has, which decides where they are told to enrol.
post
/api/v0/main-frontend/credit-registrations/my/by-course-module/{course_module_id}/enrolment-route/confirm
POST `/api/v0/main-frontend/credit-registrations/my/by-course-module/{course_module_id}/enrolment-route/confirm` - The caller says they have enrolled. Counts as a check request: a waiting registration restarts its checks on the check-requested schedule, under the limit every check request shares. Recorded against the completion too, so a registration that starts waiting later starts on that schedule. For a caller with no linked student number, it also makes the course code's enrolment list due sooner.
delete
/api/v0/main-frontend/credit-registrations/my/by-course-module/{course_module_id}/enrolment-route/confirm
DELETE `/api/v0/main-frontend/credit-registrations/my/by-course-module/{course_module_id}/enrolment-route/confirm` - The caller takes back saying they had enrolled.
get
/api/v0/main-frontend/credit-registrations/my/enrolment-banners/by-course/{course_id}
GET `/api/v0/main-frontend/credit-registrations/my/enrolment-banners/by-course/{course_id}` - The caller's registrations on one course that owe them the in-course re-enrol banner. Scoped to the course rather than filtered from `/my` on the client, because every course-material page view calls this. Empty is the normal answer.
get
/api/v0/main-frontend/credit-registrations/my/student-number
GET `/api/v0/main-frontend/credit-registrations/my/student-number` - The student number linked to the signed-in account, or null.
delete
/api/v0/main-frontend/credit-registrations/my/student-number
DELETE `/api/v0/main-frontend/credit-registrations/my/student-number` - Unlinks the student number from the signed-in account. Registrations that have not been sent go back to waiting; credits already in Sisu are untouched.
post
/api/v0/main-frontend/credit-registrations/my/{id}/dismiss-enrolment-banner
POST `/api/v0/main-frontend/credit-registrations/my/{id}/dismiss-enrolment-banner` - Puts away the in-course re-enrol banner for one registration. Idempotent. Not a permanent opt-out: a later entry into the same state clears the dismissal.
post
/api/v0/main-frontend/credit-registrations/my/{id}/recheck-enrolment
POST `/api/v0/main-frontend/credit-registrations/my/{id}/recheck-enrolment` - Asks the pipeline to look for an enrolment again, for a row parked because the study registry had none.
get
/api/v0/main-frontend/credit-registrations/settings
GET `/api/v0/main-frontend/credit-registrations/settings` - Deployment-wide credit registration switches.
get
/api/v0/main-frontend/credit-registrations/student-number-verifications/{token}
GET `/api/v0/main-frontend/credit-registrations/student-number-verifications/{token}` - What the mailed link would link, without linking it. Writes nothing: the link has to survive a mail scanner fetching it.
post
/api/v0/main-frontend/credit-registrations/student-number-verifications/{token}/claim
POST `/api/v0/main-frontend/credit-registrations/student-number-verifications/{token}/claim` - Spends a mailed link and links the student number to the signed-in account. Any signed-in account may claim any valid token: holding it proves control of the Sisu-held mailbox, and the session says which of our accounts the person wants to use.
email_templates
3
email-verification
4
exams
11
exercise_repositories
5
exercise_services
5
exercise_slide_submissions
3
exercises
11
feedback
1
files
2
global-stats
7
glossary
4
oauth
17
org
1
organizations
16
page_audio
3
pages
8
playground-examples
4
playground-views
2
proposed_edits
3
regradings
4
roles
4
shared_submissions
4
status
11
teacher_grading_decisions
1
time
1
user-details
10
users
18
credit-registrations
Copy Markdown
Copied
Copy failed
Changes to GET `/api/v0/main-frontend/credit-registrations/settings` - Deployment-wide credit registration switches.
get
/api/v0/main-frontend/credit-registrations/settings
Sep 29, 2026
a9e34d23136a
Revision changes
○
endpoint added
Ask about this API