Kralis for Developers

The integration model

Part	Who owns it	Purpose
Kralis GraphQL API	Kralis	Main product queries, mutations, business rules, and school data
Kralis authentication	Kralis	One SimpleJWT family available through GraphQL or REST authentication
Kralis Web	Kralis	A complete interface schools can use for setup and everyday work
Your client	Your development team	A custom experience built for the school or its users
School configuration	Authorized school operators	Years, terms, classes, users, roles, modules, and operational data

Your client and Kralis Web work with the same school data. A school can keep using kralis.app even when it also has a custom frontend.

Start here

Goal	Guide
Onboard a school and make the first API call	Developer Quickstart
Sign in and manage tokens safely	Authentication
Browse every operation and test GraphQL auth	Exploring GraphQL with GraphiQL
Keep every operation inside the correct school	School Scoping and Authorization
Choose between the two API surfaces	GraphQL and REST
Structure a dependable frontend or mobile client	Building a Client
Handle errors, pagination, and changing data	Errors and Pagination
Integrate supported Classroom workflows	Classroom API Integration
Open the live schema and API references	API Reference Links
Review the developer offering and support path	API Access, Templates, and Support

What is not required

cloning or running Kralis repositories;

connecting directly to the Kralis database;

managing Kralis infrastructure; or

recreating server-side permissions in place of API authorization.

Enterprise arrangements can provide a separately operated school instance, but Kralis still handles its infrastructure and maintenance. Integration remains API-based.

​The integration model

​Start here

​What is not required

The integration model

Start here

What is not required