CoreCampus SIS Integration API
66
AI ReadinessAI-Aware (B)66/100
Agent-ready OpenAPI document · curated by JenticEducationStudent ManagementapiKey7 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Sync student records, enrollments, courses and grades from CoreCampus SIS into LMS, reporting or analytics systems through a small set of REST endpoints.
Use for: Create a new student record in CoreCampus from the admissions feed, Update a student's email address in CoreCampus after a name change, List all enrollments for the current term to build a course roster, Retrieve the course catalogue from CoreCampus for a term
Not supported: Does not handle financial aid, billing, or learning content delivery - use for student, enrollment, course catalogue and grade record sync only.
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.
Install Jentic One Beta
Connect the CoreCampus SIS Integration API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CoreCampus SIS Integration API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcorecampus.com%2Fcorecampus" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcorecampus.com%2Fcorecampus" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with CoreCampus SIS Integration API.
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
Patterns agents use CoreCampus SIS Integration API for, with concrete tasks.
★ 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.
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.
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.
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.
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
7 endpoints — jentic publishes the only available openapi specification for corecampus sis integration api, keeping it validated and agent-ready.
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
CoreCampus SIS Integration API
- AI-Aware (B)66/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
29%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
58%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using CoreCampus SIS Integration API through Jentic.
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.
GET STARTED