Classe365 API

Name: Classe365 API API
Brand: Classe365 API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentEducationStudent Managementbasic38 EndpointsREST

For Agents

Manage students, staff, attendance, assessments, fees, and academic structure inside Classe365 institutions. Useful for SIS sync, enrollment automation, and finance reporting workflows.

Quickstart

Get started with Classe365 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:
"enroll a student in Classe365"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Classe365 API API.

Add or update student, teacher, administrator, and agent records

Enroll students in courses and manage elective subject allocation

Record and query attendance by date, student, or class

Save and retrieve assessment scores at student or subject level

Create fee invoices and inspect ledger accounts and entries

GET STARTED

Start building with Classe365 API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Classe365 API, keeping it validated and agent-ready.

Classe365 is a school and higher-education management platform, and its REST API exposes the operational core of the system. It covers student and staff records, course enrollment, attendance, assessment scoring, fee invoicing, ledger accounting, and form submissions. Each customer accesses the API through a tenant-specific subdomain so data stays isolated per institution. The API is suited to schools, colleges, and tutoring businesses that want to sync their student information system with admissions, finance, or analytics tooling.

Use Cases

Patterns agents use Classe365 API API for, with concrete tasks.

★ Admissions to enrollment automation

Schools commonly capture admissions in an external CRM or web form, then have to copy the accepted applicant into their SIS. With Classe365, the accepted record can be pushed via POST /rest/student and immediately enrolled into a course using POST /rest/studentCourseEnroll. This eliminates double entry and keeps academic records in sync from day one of the term.

Read accepted applicants from the admissions CRM and call POST /rest/student followed by POST /rest/studentCourseEnroll for each, then return a summary of enrollments

Daily attendance ingestion

Classe365 supports both individual and bulk attendance updates. Schools that take attendance in a separate mobile app can push the day's data with POST /rest/manageAttendance and verify it back with GET /rest/allAttendanceByDate. This gives administrators a single source of truth and lets them generate parent notifications from the canonical Classe365 record.

Push today's attendance for grade 9 from the mobile app and confirm via GET /rest/allAttendanceByDate that all records were saved

Fee invoice generation and reconciliation

Finance teams generate term tuition invoices and reconcile them against the institution's ledger. POST /rest/createInvoice issues an invoice for a student or cohort, and GET /rest/feeInvoicesData plus GET /rest/accountEntries supply the data needed for accounting reconciliation. Running this on a schedule keeps the ledger and student finance records in agreement.

Create term-1 invoices for all active students and reconcile the resulting entries from GET /rest/accountEntries against the bank feed

Assessment scoring and reporting

Teachers enter assessment scores either through the Classe365 UI or via API. POST /rest/saveAssessmentScore writes results, and GET /rest/studentScore or GET /rest/subjectScore retrieves them for report-card generation. This pattern lets schools build custom report formats outside the Classe365 templates while keeping scores authoritative inside the platform.

Save end-of-term assessment scores for class 10A and pull GET /rest/subjectScore to populate the custom report card template

AI agent integration via Jentic

An admissions chatbot built on Jentic searches by intent, loads the schema for student creation, and onboards applicants straight into Classe365. Because authentication is HTTP basic (tenant_name:api_key), the credentials are kept in the Jentic vault and the agent never receives them. The same agent can call assessment, fee, and attendance endpoints by re-running the search with new intents.

Receive 'enroll Aanya Patel in Grade 9 Maths starting Aug 1' from chat, search Jentic for Classe365 student creation and enrollment, and execute both calls in sequence

Key Endpoints

38 endpoints — classe365 is a school and higher-education management platform, and its rest api exposes the operational core of the system.

METHOD

PATH

DESCRIPTION

POST

/rest/student

Add or update a student record

POST

/rest/studentCourseEnroll

Enroll students in courses

POST

/rest/manageAttendance

Add or update attendance

GET

/rest/studentsData

Retrieve student data in bulk

POST

/rest/saveAssessmentScore

Save assessment scores

POST

/rest/createInvoice

Create a fee invoice

GET

/rest/accountEntries

Retrieve ledger account entries

POST

/rest/teacher

Add or update a teacher

POST

/rest/student

Add or update a student record

POST

/rest/studentCourseEnroll

Enroll students in courses

POST

/rest/manageAttendance

Add or update attendance

GET

/rest/studentsData

Retrieve student data in bulk

POST

/rest/saveAssessmentScore

Save assessment scores

Why though Jentic?

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

Credential isolation

Classe365 basic-auth credentials (tenant_name:api_key) are stored encrypted in the Jentic vault. Agents call operations through Jentic without ever holding the API key in their prompt context, which is critical for institutions handling student PII.

Intent-based discovery

Agents query Jentic with intents like 'enroll a student' or 'create a fee invoice' and Jentic returns the matching Classe365 operation with its input schema, so the right endpoint is selected without browsing the 38-endpoint surface.

Time to first call

Direct Classe365 integration: 2-4 days for tenant configuration, basic-auth wiring, and per-resource error handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

PowerSchool SIS API

Established K-12 student information system with deep US-district adoption

Choose PowerSchool for US K-12 districts already standardised on it; choose Classe365 for higher-ed and international school networks

Alternative

Schoology API

Learning management system focused on classroom workflows

Choose Schoology when LMS-style course content delivery is the primary need; pick Classe365 when financial and admissions data matter equally

Complementary

Moodle API

Open-source LMS for course content and grading

Pair Moodle with Classe365 to combine open-source LMS course delivery with Classe365's SIS and finance backbone

FAQs

Specific to using Classe365 API API through Jentic.

What authentication does the Classe365 API use?

Classe365 uses HTTP basic authentication where the username is your tenant_name and the password is the API key generated from Admin Panel > Settings > APIs. The base64-encoded credential is sent in the Authorization header. Through Jentic, this credential is stored in the encrypted vault so agents never see the raw API key.

Is the Classe365 API multi-tenant?

Yes. The base URL is https://{tenant_name}.classe365.com so each institution gets its own subdomain and isolated dataset. Any API call must include the tenant in the host, which means agents working across multiple institutions must rotate the host alongside the credential.

Can I record attendance in bulk through the Classe365 API?

Yes. POST /rest/manageAttendance accepts attendance records and is paired with GET /rest/allAttendanceByDate and GET /rest/attendanceByDateInLV for retrieval. This supports bulk daily ingestion patterns where attendance is captured externally and synced into Classe365.

How do I create a fee invoice in Classe365?

Call POST /rest/createInvoice with the student or cohort details and the fee head. The resulting invoice is queryable via GET /rest/feeInvoicesData, and the corresponding ledger movement appears in GET /rest/accountEntries for reconciliation against your accounting system.

How do I enroll a student through Jentic?

Install the SDK with pip install jentic, then search Jentic for 'enroll a student in classe365', load the returned schema, and execute. Jentic injects the basic-auth credential at execution time, so your agent does not need to handle the API key directly.

Can the Classe365 API save assessment scores?

Yes. POST /rest/saveAssessmentScore writes assessment scores, and GET /rest/studentScore, GET /rest/studentsScore, and GET /rest/subjectScore return scores at varying granularities. This lets you build custom report cards while keeping Classe365 as the source of truth for grades.