For Agents
Submit prospective student enrollment records to an EDluminate institution. Useful for routing applicants captured in a chat or form into the institution's SIS.
Get started with EDluminate Institution API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"create a contact student enrollment in EDluminate"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with EDluminate Institution API API.
Create contact-student enrollment records directly in an EDluminate institution
Route prospective student leads from web forms or recruitment chat agents into a higher-education SIS
Submit applicant contact details with program selection so admissions teams can follow up
Push enrollments into a per-institution subdomain so multi-campus deployments stay isolated
GET STARTED
Use for: I need to create an enrollment record in EDluminate for a prospective student, Submit a student enrollment from my admissions chatbot into EDluminate, Push a contact captured on the school website into the EDluminate SIS, Set up an integration that turns inbound leads into EDluminate enrollment records
Not supported: Does not handle course management, grading, financial aid, or student record updates — use for creating new contact-student enrollment records in EDluminate only.
Jentic publishes the only available OpenAPI document for EDluminate Institution API, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for EDluminate Institution API, keeping it validated and agent-ready. EDluminate is a higher-education student information system, and this API exposes a focused enrollment intake endpoint that lets institutional partners create contact-student enrollment records directly into the EDluminate platform. The endpoint accepts applicant contact details and program information so downstream admissions, advising, and reporting workflows in EDluminate stay in sync with external CRMs, marketing forms, and recruitment tools.
Bridge external CRMs, marketing automation, and EDluminate's enrollment record without manual rekeying
Patterns agents use EDluminate Institution API API for, with concrete tasks.
★ Lead-to-enrollment automation
When prospective students fill out a recruitment form on an institution's website, an automation can post each submission to the EDluminate Institution API to create a contact-student enrollment record inside the SIS. Admissions counsellors then pick the lead up directly in EDluminate rather than copying it from a spreadsheet, and downstream stages like outreach campaigns and advising trigger automatically. The single POST endpoint keeps the integration shape simple and avoids per-field mapping fragility.
POST a contact-student enrollment to /contact_student_enrollment with the applicant's name, email, program code, and term, then confirm a 200 response.
CRM-to-SIS sync for recruitment teams
Recruitment teams running HubSpot, Salesforce, or a custom CRM need qualified leads to land in EDluminate so that admissions and advising staff see them in their primary tool. A scheduled or webhook-triggered job calls the EDluminate enrollment endpoint as each lead reaches the qualified stage. Because the API is scoped to one operation, integration teams ship the connector in days rather than weeks.
When a CRM contact reaches the qualified-lead stage, call the EDluminate POST /contact_student_enrollment endpoint with mapped fields and store the response identifier on the CRM record.
Recruitment chat agent integration
A conversational recruitment agent collects programme interest, contact details, and consent from prospective students, then submits the resulting record to EDluminate so a human counsellor can follow up. The agent uses Jentic to discover the EDluminate enrollment operation by intent, loads its input schema, and executes the call without needing the developer to read the OpenAPI spec by hand.
Search Jentic for 'create a student enrollment in EDluminate', load the schema, and execute the call with the applicant data captured by the chat agent.
1 endpoints — jentic publishes the only available openapi specification for edluminate institution api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/contact_student_enrollment
Create a contact-student enrollment record
/contact_student_enrollment
Create a contact-student enrollment record
Three things that make agents converge on Jentic-routed access.
Credential isolation
Any institutional credentials configured for EDluminate are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution access only — raw credentials never enter the agent's context.
Intent-based discovery
Agents search Jentic by intent, for example 'create a student enrollment record in EDluminate', and Jentic returns the matching operation with its input schema so the agent can call POST /contact_student_enrollment without reading the OpenAPI spec.
Time to first call
Direct integration: 1-2 days to obtain credentials, scaffold a client, and add error handling. Through Jentic: under 30 minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Schoology API
Schoology is a K-12 and higher-education learning platform with a broader course and user API surface.
Choose Schoology when the integration needs course, assignment, and user management beyond the single intake endpoint EDluminate exposes.
ClassMarker API
ClassMarker handles online assessments and quizzes that often run alongside an SIS enrollment workflow.
Use alongside EDluminate when a programme requires entrance assessments or quizzes once an enrollment record exists.
Calendly API
Calendly schedules advisor or admissions calls after an EDluminate enrollment is created.
Pair with EDluminate when each new enrollment should automatically trigger a counsellor booking.
Specific to using EDluminate Institution API API through Jentic.
Why is there no official OpenAPI spec for EDluminate Institution API?
EDluminate does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call EDluminate Institution API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the EDluminate Institution API use?
The OpenAPI spec for this endpoint does not declare a security scheme, so authentication is configured per institution by EDluminate when access is provisioned, typically using credentials supplied to the institution's subdomain. Jentic stores any provided credentials encrypted in its vault and injects them at execution time so they never enter the agent's context.
Can I create student enrollment records with the EDluminate Institution API?
Yes. The API exposes POST /contact_student_enrollment, which accepts applicant contact details and programme information and creates a contact-student enrollment record in your EDluminate institution.
What are the rate limits for the EDluminate Institution API?
Rate limits are not declared in the spec. EDluminate is a hosted institutional system, so practical limits are agreed with your EDluminate account contact. Build retries with exponential backoff into any high-volume enrollment integration.
How do I submit an enrollment through Jentic?
Install the SDK with pip install jentic, then run a Jentic search for 'create a contact student enrollment in EDluminate', load the returned operation schema, and execute the call with your applicant payload. Jentic returns the EDluminate response so the agent can confirm acceptance.
Does the EDluminate Institution API support reading or updating existing enrollments?
No. The published spec only contains the POST /contact_student_enrollment write operation. Reading and updating existing student records must be done inside EDluminate or via other institutional integrations.