Skip to main content
Kralis exposes authentication through its REST auth surface.

​
Primary auth surface

This area is used for:
  • login
  • logout
  • token lifecycle
  • current user details
  • password-related operations

​
Integrator expectation

A client should authenticate first, capture the resulting user and school context, and then use that context when calling GraphQL or other supported resources.

​
Important rule

Treat returned user and school context as operationally important. Many follow-up flows depend on knowing which school, role, year, and term the current user is working inside.