canonical: https://jentic.com/apis/powerschool.com/powerschool # PowerSchool SIS API Jentic publishes the only available OpenAPI specification for PowerSchool SIS API, keeping it validated and agent-ready. The PowerSchool SIS API provides programmatic access to K-12 student information system data including student demographics, school rosters, course sections, enrollment records, and daily attendance. It enables education technology platforms to synchronize student data across district-wide systems with OAuth 2.0 client credentials authentication and paginated responses. ## For AI agents Retrieve student records, school rosters, section enrollments, and attendance data from PowerSchool student information systems. ## Scope Does not handle grade book entries, assignment submissions, or fee payments -- use for student data retrieval only. ## Capabilities - Pull district-wide student rosters with pagination for large datasets - Retrieve individual student demographic and enrollment details by ID - List all schools within a district for organizational mapping - Query course sections assigned to a specific school - Access section enrollment records to determine class composition - Fetch daily attendance records for individual students ## Use cases ### Student Data Synchronization Synchronize student demographic and enrollment records from PowerSchool SIS to third-party learning management systems or assessment platforms. The API provides paginated access to district-wide student lists and individual student details, enabling daily or hourly sync operations that keep downstream systems current without manual data entry. Example prompt: Retrieve the full student list from /district/student with page=1 and pagesize=100, then fetch detailed records for each student via /student/{id} ### Attendance Monitoring Monitor student attendance patterns by pulling attendance records from PowerSchool SIS. The API returns attendance data per student, enabling early-warning systems that flag chronic absenteeism and alert counselors or administrators when students exceed absence thresholds. Example prompt: Fetch attendance records for student ID 12345 via /student/12345/attendance and check for absences exceeding 3 days in the current month ### Course Section Enrollment Reporting Generate enrollment reports by querying section enrollment data for each school and section. The API enables administrators and reporting tools to determine class sizes, identify over-enrolled sections, and support scheduling decisions across the district. Example prompt: List sections for school ID 5 via /school/5/section, then retrieve enrollments for each section via /section/{id}/section_enrollment to compile a class-size report ### AI Agent Integration for Student Data Access Enable AI agents to query PowerSchool SIS data through Jentic for tasks like generating progress reports, answering parent inquiries about attendance, or populating dashboards. Agents search for the relevant operation via Jentic, load the schema, and execute against the district's PowerSchool instance. Example prompt: Search Jentic for 'retrieve student attendance data', load the PowerSchool SIS operation schema, and execute a call to /student/{id}/attendance for the target student ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /district/student | List all students in the district with pagination | | GET | /student/{id} | Retrieve a single student record by ID | | GET | /district/school | List all schools in the district | | GET | /school/{id}/section | List course sections for a school | | GET | /section/{id}/section_enrollment | List enrollments for a section | | GET | /student/{id}/attendance | Get attendance records for a student | ## Key resources - **Students** — District-wide student records with demographics and enrollment info - **Schools** — Schools within the district - **Sections** — Course sections offered at each school - **Enrollments** — Student-to-section enrollment mappings - **Attendance** — Daily attendance records per student ## Why Jentic - **Setup:** Wiring the PowerSchool SIS API by hand means running its OAuth 2.0 client-credentials flow, substituting your district's {server} host into every URL, and refreshing tokens yourself. Through Jentic you install once, import the PowerSchool SIS API from the API Directory, store the client id and secret once, and your agent calls it. - **Permission scoping:** PowerSchool puts the student, school, and section ids in the URL path (/student/{id}, /school/{id}/section), so a rule can pin your agent to one student's records: it can read that student's details and attendance and nothing else. This spec exposes only read operations, so no write to student data is included. - **Credential handling:** Your PowerSchool client id and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get student attendance records' or 'list schools in a district', and Jentic returns the matching PowerSchool SIS operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Schoology API** — Learning management system that consumes student data from SIS platforms like PowerSchool - **Clever API** — Middleware that normalizes student data from multiple SIS platforms into a single API - **Calendly API** — Scheduling platform for parent-teacher conferences and student meetings ## FAQ ### Why is there no official OpenAPI spec for PowerSchool SIS API? PowerSchool does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call PowerSchool SIS 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 PowerSchool SIS API use? The PowerSchool SIS API uses OAuth 2.0 with a client credentials flow. You obtain an access token by sending your client ID and secret to the token endpoint at /oauth/access_token on your PowerSchool server instance. Through Jentic, these credentials are stored encrypted in the credential vault and agents receive scoped tokens without handling raw secrets. ### Can I retrieve attendance data for a specific student with the PowerSchool SIS API? Yes. The GET /student/{id}/attendance endpoint returns attendance records for a specific student identified by their PowerSchool ID. The response includes dates, attendance codes, and period information. ### What are the rate limits for the PowerSchool SIS API? PowerSchool applies rate limiting at the server level, typically allowing a set number of concurrent connections per plugin. The exact limits depend on your district's server configuration and PowerSchool version. Contact your district administrator for specific thresholds. ### How do I list all students in a district through Jentic? Install the Jentic SDK with pip install jentic, then search for the operation using the query 'list students in district'. Jentic returns the GET /district/student operation with its full input schema including page and pagesize parameters. Execute the call to retrieve paginated student records. ### Does the PowerSchool SIS API support write operations? This spec covers read-only endpoints for students, schools, sections, enrollments, and attendance. PowerSchool does support write operations through additional API extensions, but this specification focuses on the core data retrieval endpoints most commonly needed for integrations. ### Can I limit what my agent is allowed to do with the PowerSchool SIS API? Yes. Because you run Jentic One yourself, your own rules decide which PowerSchool operations and credentials the agent may use. Since PowerSchool puts the student, school, and section IDs in the URL path (/student/{id}, /school/{id}/section), you can pin the agent to a single student's records so it reads only that student's details and attendance and nothing else. This spec exposes only read operations, so the agent cannot write to student data at all.