School onboarding is available through GraphQL only. There is no REST
onboarding equivalent.
Public operations
These operations may be called anonymously, but they cannot be combined in one request with protected operations. Public request limits still apply.
Suggest an acronym
onboardSchool.
Check an acronym
reason when available is false.
Create the school
accessCode is present only when onboarding starts a supported payment transaction. When it is null, continue to the success screen without opening a payment flow.
Validation errors
Onboarding validation uses a stable GraphQL error code and field details:fieldErrors to the corresponding controls and show the top-level message as a form summary. For a transport or unexpected server failure, keep the entered draft and offer a safe retry rather than submitting repeatedly in the background.
After onboarding
Use the returnedadminId and adminPin with the GraphQL login mutation. Then complete years, terms, classes, users, permissions, modules, and billing configuration in Kralis Web before relying on those records in a custom client.
See Authentication and Developer Quickstart.
