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

# Element451 API

Jentic publishes the only available OpenAPI specification for Element451 API, keeping it validated and agent-ready. Element451 is an AI-powered student-engagement platform for higher education that exposes 605 endpoints covering admissions applications, CRM contacts, campaigns, decisions, events, forms, courses, campuses, and admin user management. The API spans the full enrolment lifecycle - from form-based inquiries and supplemental application sections to decision letters, fee waivers, and post-enrolment automation. Tenant URLs are subdomain-scoped (https://{client}.element451.com) and all calls authenticate with an API key passed in the Authorization header.

## For AI agents

Run an end-to-end higher-ed admissions and student-engagement workflow: manage applications, decisions, contacts, campaigns, events, and forms across an Element451 tenant. Authenticated with an API key in the Authorization header.

## Scope

Does not handle student information system records for enrolled students, learning management, grading, or financial aid disbursement - use for higher-ed admissions, CRM, and engagement only.

## Capabilities

- Create and update student applications including step-by-step section data and supplemental forms
- Issue admissions decisions, render application previews, and process fee waivers
- Manage internal admin users and per-tenant API keys via `/v2/admins/apikeys`
- Run multi-channel campaigns and segment audiences through CRM contact records
- Schedule appointments, events, and campus visits tied to a prospect record
- Configure custom forms, conditions, and autoresponders for lead capture and nurture
- Pull course, campus, and degree catalogue data to drive program-finder experiences

## Use cases

### End-to-End Admissions Processing

Operate the full admissions funnel from inquiry to decision inside Element451. Agents and integrations create applications, attach supplemental forms, preview the rendered application, apply fee waivers where eligible, and post final decisions back to the applicant record. With 605 endpoints covering steps, sections, and supplemental forms, the API supports multi-stage applications across undergraduate, graduate, and continuing-education programs.

Example prompt: Create a new application for applicant_id=12345 against registration_id=fall-2026-grad, save answers to two supplemental forms, apply a fee waiver, then issue an Accept decision

### Recruitment CRM and Campaign Automation

Use Element451 as a higher-ed CRM by syncing inquiries from web forms, segmenting prospects by program interest, and triggering nurture campaigns through the campaigns and forms endpoints. The API supports per-application autoresponder configuration so a yield campaign can be tuned independently for each program. Suitable for institutions managing tens of thousands of prospects per cycle.

Example prompt: Find all contacts who completed a program-interest form for 'Computer Science MS' in the last 30 days and enrol them in the 'CS-MS-Yield' campaign

### Admin and Access Management

Provision internal staff accounts and rotate per-tenant API keys for integrations on the Element451 platform. The `/v2/admins` and `/v2/admins/apikeys` endpoints support full create, update, and delete on both internal users and the keys they hold, which lets IT teams enforce least-privilege access and rotate credentials on schedule.

Example prompt: Create a new internal admin user 'analytics-bot' with read-only role, then create a fresh API key tied to that user and revoke the previous key

### AI Agent Integration via Jentic

Build an AI advisor that answers prospective-student questions, looks up the contact record by email, and books a campus tour by calling Element451's appointments endpoint. Through Jentic, the agent searches by intent, loads the appointment-creation schema, and executes without holding the tenant API key in its prompt.

Example prompt: Search Jentic for 'schedule a campus tour appointment', load the input schema for the Element451 appointments endpoint, and book a tour for contact_id=98765 next Tuesday at 2pm

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v2/admins/apikeys` | Create an API key |
| GET | `/v2/admins` | List internal admin users |
| POST | `/v2/applications/{APPLICATION_GUID}/payment/waiver` | Apply a fee waiver to an application |
| GET | `/v2/applications/{APP_GUID}/preview` | Generate an HTML preview of an application |
| POST | `/v2/users/applications/{REGISTRATION_ID}/supplementalforms/{ITEM_ID}` | Save a supplemental form answer on an application |
| GET | `/v2/applications/settings/autoresponders/{application_guid}` | Get autoresponders for an application |

## Key resources

- **Applications** — Create, update, preview, decision, and waive admissions applications including steps, sections, and supplemental forms
- **Admins** — Manage internal staff users and per-user API keys
- **Campaigns** — Run multi-channel marketing and recruitment campaigns
- **Contacts and Users** — Look up and update prospect, applicant, and admitted-student records
- **Events and Appointments** — Schedule campus visits, virtual events, and one-on-one meetings
- **Forms** — Configure inquiry, application, and supplemental forms with conditions and autoresponders
- **Catalogue** — Read campuses, courses, degrees, and decisions data

## Why Jentic

- **Setup:** Wiring Element451 by hand means pointing at your own client subdomain, handling its API-key auth in the Authorization header, and mapping intents across a wide admissions surface yourself. Through Jentic you install once, import the Element451 API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Element451 puts the application id in the URL path (`/v2/applications/{APPLICATION_GUID}/payment/waiver`, `/v2/applications/{APP_GUID}/preview`), so a rule can pin your agent to one application. You choose the operations it may call, so admin operations like POST `/v2/admins/apikeys` are not included unless you add them.
- **Credential handling:** Your Element451 API key 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.
- **Discovery method:** Agents search Jentic by intent such as 'preview an application' or 'waive an application payment', and Jentic returns the matching Element451 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Salesforce API** — Salesforce Education Cloud is a generalist alternative to a higher-ed-native CRM
- **HubSpot Marketing Emails API** — HubSpot can drive top-of-funnel marketing while Element451 handles applications and decisions
- **PowerSchool SIS API** — PowerSchool manages enrolled student records; Element451 manages the recruit-to-enrol funnel

## FAQ

### Why is there no official OpenAPI spec for Element451 API?

Element451 publishes its API reference as a Postman collection on Postman Documenter rather than as a versioned OpenAPI specification. Jentic generates and maintains this OpenAPI spec so AI agents and developers can call Element451 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 Element451 API use?

Element451 uses an API key passed in the Authorization request header. Each key is tied to an internal admin user and inherits that user's permissions, so least-privilege rotation is straightforward. Through Jentic, the API key is stored in the encrypted vault and never exposed to the agent's prompt.

### Can I issue admissions decisions through the Element451 API?

Yes. The Decisions and Get Decision endpoint groups expose the operations needed to read, set, and update an applicant's decision status, and the related autoresponder endpoints fire decision letters automatically once the status changes.

### What is the base URL for the Element451 API?

The base URL is https://{client}.element451.com where {client} is the institution's tenant subdomain. Every request is scoped to that tenant, so a key issued for one institution will not work against another.

### How do I book a campus tour through Element451 via Jentic?

Run the Jentic search query 'schedule a campus tour appointment', load the input schema for the appointments endpoint, then execute with the contact_id and the desired time. The booking is reflected on the contact record and triggers the configured autoresponder.

### Are supplemental forms supported on every application?

Supplemental forms are configurable per registration and can be attached, detached, and answered via `/v2/users/applications/{REGISTRATION_ID}/supplementalforms.` Programs without supplemental requirements simply have no items in that collection.

### Can I limit what my agent is allowed to do with the Element451 API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Element451 operations and credentials the agent may use. Because the API puts the application id in the URL path (for example `/v2/applications/{APPLICATION_GUID}/payment/waiver` and `/v2/applications/{APP_GUID}/preview`), you can pin the agent to a single application. You also choose the exact operations it can call, so admin actions such as POST `/v2/admins/apikeys` stay off limits unless you explicitly add them.