The Admissions module manages the full pipeline for bringing new students into Gobarau Academy and for registering former students in the alumni directory. It provides three focused resources:Documentation Index
Fetch the complete documentation index at: https://mintlify.com/muhammadbugaje/gobarau_backend/llms.txt
Use this file to discover all available pages before exploring further.
Application records capture a prospective student’s personal details and the class they are applying for; EntranceExam records attach exam scheduling and scoring information to an application; and AlumniRegistration records allow graduates to submit their post-school details for inclusion in the alumni directory pending staff review. Together, these endpoints support the end-to-end flow from first inquiry to official enrollment and beyond.
All three admissions endpoints require an authenticated user with Staff or Admin privileges (
IsStaffOrAdmin permission class). Include a valid Bearer token in every request.Authentication & Permissions
IsAuthenticated and IsStaffOrAdmin. Unauthenticated requests receive 401 Unauthorized; authenticated non-staff users receive 403 Forbidden.
Applications
TheApplication resource is the entry point for the admissions pipeline. Each application captures the prospective student’s biographical information, the class they are applying for, and the academic session. Once submitted, applications move through a review workflow managed by staff.
List / Create Applications
Retrieve / Update / Delete Application
Request Fields
Full name of the prospective student (max 200 characters).
Applicant’s date of birth in ISO 8601 format, e.g.
"2010-03-15". Optional.Applicant’s gender. One of:
Defaults to an empty string if not provided.
| Value | Label |
|---|---|
M | Male |
F | Female |
Contact phone number (max 20 characters). Optional.
Contact email address. Optional.
Residential address of the applicant or family. Optional.
State of origin using the Nigerian state slug, e.g.
"kano", "lagos", "fct". Must be one of the 37 Nigerian states/FCT values. Optional.Local Government Area of origin (max 100 characters). Optional.
Applicant’s religion (max 50 characters). Optional.
Foreign key to
administration.Wing. The school wing the applicant is applying to (e.g. Regular, Islamiyyah, Tahfeez). Nullable.Foreign key to
administration.ClassLevel. The class level the applicant is seeking entry into. Nullable.Foreign key to
administration.AcademicSession. The intake session for this application.Current status of the application in the review workflow. One of:
| Value | Label |
|---|---|
pending | Pending |
accepted | Accepted |
rejected | Rejected |
waitlisted | Waitlisted |
Foreign key to
accounts.User. The staff member who reviewed this application. Nullable — set automatically during the review process.ISO 8601 datetime of when the application was reviewed. Nullable — set automatically during the review process.
submitted_at is set automatically to the current timestamp (auto_now_add=True) and cannot be provided in the request body.Example — Create an Application
Example Response
Response Fields
Auto-generated primary key for the application.
Full name of the applicant as submitted.
Current pipeline status:
pending, accepted, rejected, or waitlisted.Server-assigned timestamp of when the application was created.
PK of the reviewing staff member, or
null if not yet reviewed.Timestamp of the review action, or
null if not yet reviewed.Application Workflow
Applications progress through the following status states:PATCH request to update the status, reviewed_by, and reviewed_at fields:
Entrance Exams
TheEntranceExam resource links exam scheduling and outcome data to a specific application. An application can have multiple exam records (e.g. rescheduled sittings), each with its own date, venue, score, and pass/fail result.
Request Fields
Foreign key to
admissions.Application. The application this exam record is associated with.ISO 8601 date on which the exam is scheduled or was held, e.g.
"2024-11-20".Venue or room where the exam is held (max 200 characters), e.g.
"Main Hall, Block A".The applicant’s exam score (up to 5 digits, 2 decimal places), e.g.
78.50. Nullable — may be populated after the exam is marked.Whether the applicant met the passing threshold for this exam. Updated by staff after scoring is complete.
Example — Create an Entrance Exam Record
Example Response
Example — Record Exam Results
After the exam has been marked, update the record with the score and pass/fail outcome:Alumni Registrations
TheAlumniRegistration resource allows former students to submit their details for inclusion in the school’s official alumni directory. Submissions are held in a pending state until reviewed and approved (or rejected) by administration. Upon approval, staff can use the data to create or update an AlumniProfile in the People app.
Request Fields
Foreign key to
people.StudentProfile. Links the registration to the alumnus’s original student record in the system.Four-digit year of graduation, e.g.
2020.Broad industry or career field, e.g.
"Law", "Technology" (max 200 characters). Optional.Name of current employer (max 200 characters). Optional.
Higher institution attended after Gobarau Academy (max 200 characters). Optional.
City of current residence (max 100 characters). Optional.
Country of current residence (max 100 characters).
Full LinkedIn profile URL. Optional.
A personal message from the alumnus to the school or to current students. Optional, free-text.
Review status of this registration. One of:
| Value | Label |
|---|---|
pending | Pending |
approved | Approved |
rejected | Rejected |
Foreign key to
accounts.User. The staff member who reviewed the registration. Nullable.ISO 8601 datetime of the review action. Nullable.
submitted_at is set automatically on creation and is not writable via the API.Example — Submit an Alumni Registration
Example Response
Response Fields
Auto-generated primary key for the alumni registration.
Current review status:
pending, approved, or rejected.Server-assigned timestamp when the registration was submitted.
PK of the reviewing staff member, or
null if not yet reviewed.Timestamp of the review decision, or
null if not yet reviewed.Approving a Registration
Once a registration is approved, staff should also create or update the correspondingAlumniProfile in the People API to make the alumnus visible in the main alumni directory.