Skip to main content

​
Common patterns

Start with a companion client. Rebuild only the workflows your users need, and leave complex or infrequent administration in Kralis Web until there is a clear reason to reproduce it.

​
Cross-module operations

Treat server workflows as authoritative. Examples include CBT-to-SRMS score synchronization, LMS test attachment, and Classroom event access. Do not join unrelated API responses locally and assume the result equals a supported server operation.

​
Integration checklist

  • onboard and configure the school through Kralis Web;
  • use a permitted account and least necessary role;
  • use GraphQL authentication mutations for new clients; REST /auth/ remains compatible and issues the same SimpleJWT token family;
  • use GraphQL for product queries and mutations;
  • paginate every growing connection;
  • display API validation and permission messages;
  • keep credentials and tokens out of source control;
  • verify destructive and financial actions; and
  • coordinate contract questions through Kralis support.
The live schema and OpenAPI documents are the current contracts. Do not depend on internal model names, repository layouts, infrastructure providers, or undocumented endpoints.