EDluminate Institution API

Name: EDluminate Institution API
Brand: EDluminate Institution API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentEducationStudent Managementnone1 EndpointsREST

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.

Install Jentic One Beta

Connect the EDluminate Institution API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EDluminate Institution 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 EDluminate Institution 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

GET STARTED

Start building with EDluminate Institution API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use EDluminate Institution 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.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for edluminate institution api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/contact_student_enrollment

Create a contact-student enrollment record

POST

/contact_student_enrollment

Create a contact-student enrollment record

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Any institution credential you configure for EDluminate is stored once, encrypted, by your own Jentic One instance and injected 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 student enrollment record in EDluminate', and Jentic returns the matching POST /contact_student_enrollment operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using EDluminate Institution 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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the EDluminate Institution API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API exposes only one operation, POST /contact_student_enrollment, with no resource id in its path. You allow the agent that single create-enrollment call and nothing else, so its entire reachable surface is submitting new contact-student enrollment records. Any institution credential you configure stays with your self-hosted instance and is applied at execution time rather than exposed to the agent.