canonical: https://jentic.com/apis/corecampus.com/corecampus

# CoreCampus SIS Integration API

Jentic publishes the only available OpenAPI specification for CoreCampus SIS Integration API, keeping it validated and agent-ready. CoreCampus (Campus Cafe) is a higher-education Student Information System and the integration API exposes seven endpoints across students, enrollments, courses and grades. Operations cover listing and creating students, getting and updating individual student records, and listing enrollments, courses and grades for downstream reporting or LMS sync. Authentication is via an API key, and the API is intended for institution-side integrations rather than end-user portals.

## For AI agents

Sync student records, enrollments, courses and grades from CoreCampus SIS into LMS, reporting or analytics systems through a small set of REST endpoints.

## Scope

Does not handle financial aid, billing, or learning content delivery - use for student, enrollment, course catalogue and grade record sync only.

## Capabilities

- Create a student record in CoreCampus from an external admissions system
- Update a student's profile fields when registrar information changes
- List enrollments to feed an LMS course roster or attendance system
- Pull the current course catalogue from CoreCampus for downstream display
- Retrieve grades for end-of-term reporting or transcript generation
- Look up a single student record by student ID for audit or support workflows

## Use cases

### Admissions to SIS Sync

Admissions platforms can push accepted applicants into CoreCampus by calling POST /students with the student profile. The endpoint creates the SIS record that downstream enrollment, course assignment and grading workflows depend on. PUT /students/{studentId} keeps profile changes in sync as the student progresses.

Example prompt: POST /students with the applicant's name, date of birth, email and program ID, then store the returned studentId on the admissions record.

### LMS Roster Population

Learning management systems can populate course rosters from CoreCampus by calling GET /enrollments and GET /courses, then mapping students to course sections. This avoids manual roster uploads and keeps the LMS in step with registrar changes throughout the term.

Example prompt: GET /enrollments for term '2026-Fall', join with GET /courses, and for each course produce a roster CSV of studentId-to-courseId pairs.

### End-of-Term Grade Reporting

Registrars can pull final grades for transcript generation or accreditation reporting via GET /grades. Combined with GET /students for student demographic data, this supports cohort-level outcome reporting without exporting CSVs from the SIS UI.

Example prompt: GET /grades filtered to term '2026-Spring', join each grade with GET /students/{studentId}, and emit a transcript-ready CSV per cohort.

### AI Student Support Agent

An admin-side AI agent supporting registrar staff can answer 'what are this student's grades?' or 'create a new transfer student' by calling CoreCampus through Jentic. The agent searches by intent, loads the operation schema, and executes against the right /students or /grades endpoint while Jentic injects the API key.

Example prompt: Use Jentic to call GET /students/{studentId} for the queried student, then GET /grades for the same student, and summarise their current term performance.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /students | List students |
| POST | /students | Create a student |
| GET | /students/{studentId} | Get a student by ID |
| PUT | /students/{studentId} | Update a student |
| GET | /enrollments | List enrollments |
| GET | /courses | List courses |
| GET | /grades | List grades |

## Key resources

- **Students** — Student CRUD endpoints (list, create, get, update)
- **Enrollments** — List enrollments tying students to course offerings
- **Courses** — List the course catalogue maintained in CoreCampus
- **Grades** — List grades for term reporting and transcripts

## Why Jentic

- **Setup:** Wiring CoreCampus by hand means setting its X-API-Key header and coding the student, enrollment, course, and grade sync calls yourself. Through Jentic you install once, import the CoreCampus SIS Integration API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** CoreCampus operations work over student, enrollment, course, and grade records with the target carried in the request or as a record id, so scope this by operations: allow the agent the calls it needs, such as listing enrollments and reading grades, and leave student creation or updates out unless you add them. Each operation you credit the agent with stays inside that allowed set.
- **Credential handling:** Your CoreCampus API key is stored once, encrypted, by your own Jentic One instance and injected into the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a CoreCampus student' or 'list CoreCampus enrollments', and Jentic returns the matching students, enrollments, courses, or grades operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **PowerSchool SIS API** — K-12 focused SIS alternative with broader feature coverage and district-level scale
- **Schoology API** — LMS that consumes SIS rosters and grades for online course delivery
- **Clever API** — Identity and rostering bridge between SIS data and learning applications
- **Moodle API** — Open-source LMS that can ingest CoreCampus enrollments and post back grades

## FAQ

### Why is there no official OpenAPI spec for CoreCampus SIS Integration API?

CoreCampus does not publish an OpenAPI specification at this URL. Jentic generates and maintains this spec so that AI agents and developers can call CoreCampus SIS Integration API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the CoreCampus SIS Integration API use?

The API uses an API key. Through Jentic the API key sits in the credential vault and is attached to outbound CoreCampus requests at execution time, so the secret never enters agent context.

### Can I create a new student record with the CoreCampus SIS Integration API?

Yes. POST /students accepts the student profile fields (name, contact info, program references) and returns the new studentId. Use PUT /students/{studentId} to keep that record in sync as registrar data changes.

### How do I build a course roster from CoreCampus?

Call GET /enrollments to get the student-to-course mapping for the term, then GET /courses to enrich each enrollment with course metadata, and GET /students/{studentId} to attach student details for the roster.

### What rate limits apply to the CoreCampus SIS Integration API?

The OpenAPI spec does not declare formal rate limits. Treat enrollments and grades pulls as bulk reads and run them on a schedule rather than continuously polling, with backoff on HTTP 429 responses.

### How do I list students through Jentic with the CoreCampus SIS Integration API?

Run pip install jentic, search Jentic with 'list CoreCampus students', load the operation schema for GET /students and execute it; Jentic injects the API key from the vault on the request.

### Can I limit what my agent is allowed to do with the CoreCampus SIS Integration API?

Yes. Because you run Jentic One yourself, your own rules decide which CoreCampus operations and credentials the agent can use, and it can only call the operations you grant it. You can, for example, allow read-only calls like GET /enrollments, GET /courses, and GET /grades while leaving student writes such as POST /students and PUT /students/{studentId} out of scope. Each operation the agent is credited with stays inside that allowed set, so the agent never touches records or actions you did not permit.