Skip to main content

​
Developer offering

The Kralis Developer Hub describes the current developer package, API allowance, school-size options, templates, and support benefits. Use the live page for current commercial information rather than copying plan values into a client.

​
School and developer relationship

Developers act for an onboarded school and should use accounts and data approved by that school. A developer arrangement does not permit access to unrelated schools. The platform support-school switching tools are an internal Kralis operations capability, not a developer integration feature. A custom client should keep one authenticated school context at a time and use authSchool for that context. It must never expose a school picker based on guessed acronyms or IDs, or assume that a privileged-looking account can read across schools.

​
Templates

Templates can accelerate a school website, but API authentication and private school workflows still require the same security, scoping, pagination, and error handling as any other client.

​
Ask support about

  • API access or plan questions;
  • an operation that is unclear in the live schema;
  • approved origins or deployment-specific connectivity;
  • a reproducible API failure;
  • enterprise school-instance requirements; or
  • a planned change that may affect an existing integration.
Include the school, API surface, named operation or REST path, timestamp and timezone, response status, and a sanitized error. Never send credentials or tokens.

​
Policies

Using Kralis APIs is subject to the Terms of Service and Privacy Policy.