GraphQL and REST

Kralis has two main API surfaces, but they do not carry the same workload.

​

GraphQL

GraphQL is the primary product API and should be the default choice for most application integrations. Use GraphQL for:

• application workflows
• dashboard data
• mutations that drive school operations
• most new client-facing behavior

Inspect the current schema in GraphiQL:

• GraphiQL explorer
• GraphQL endpoint

​

REST

REST is still important, but it is used more narrowly:

• authentication-related endpoints
• read-oriented resource access
• integrations
• generated OpenAPI reference

Inspect the REST contract in:

• Swagger UI
• ReDoc
• OpenAPI schema

​

Integration rule

When both GraphQL and REST exist for a workflow, prefer GraphQL unless Kralis explicitly documents REST as the intended path for that workflow.