Developer Quickstart - Kralis Docs

1. Onboard and configure the school

Create the school at kralis.app/onboard, then use Kralis Web to configure its current year and term, classes, sections, subjects, users, roles, and enabled modules.

2. Authenticate with GraphQL

Send login to /graphql/. The same operation can be explored interactively at /graphiql/.

curl https://api.kralis.app/graphql/ \
  -H "Content-Type: application/json" \
  -d '{"query":"mutation Login($input: LoginInput!) { login(input: $input) { access refresh user { pk username fullName role } school { pk schoolName } } }","variables":{"input":{"username":"YOUR_USERNAME","password":"YOUR_PASSWORD"}}}'

Keep the returned access and refresh tokens private.

3. Call GraphQL

curl https://api.kralis.app/graphql/ \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"query":"query { userBroadCasts { pk title message } }"}'

Use GraphiQL to inspect current queries, mutations, inputs, filters, and return types. Its Headers panel accepts the same Bearer token.

4. Refresh when required

Call refreshLoginToken once after an access token expires. Store both newly returned tokens before retrying the original operation.

Before production

Check	Expected outcome
Credentials	No secret or token is committed to source control
Token storage	Appropriate for a browser, server, or mobile threat model
Rotation	Both tokens are replaced after every successful refresh
School scoping	The UI uses authenticated school context rather than arbitrary school IDs
Roles	Unauthorized actions are hidden and API permission errors are handled
Pagination	Growing connections load beyond the first page
References	Operations are generated or verified against the live schema

See Authentication and API Access, Templates, and Support before production rollout.

​1. Onboard and configure the school

​2. Authenticate with GraphQL

​3. Call GraphQL

​4. Refresh when required

​Before production

1. Onboard and configure the school

2. Authenticate with GraphQL

3. Call GraphQL

4. Refresh when required

Before production