> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kralis.app/llms.txt
> Use this file to discover all available pages before exploring further.

# GraphQL and REST

> How external developers should use the two Kralis API surfaces and where to inspect the live contracts.

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](https://api.kralis.app/graphiql/)
* [GraphQL endpoint](https://api.kralis.app/graphql/)

## 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](https://api.kralis.app/schema/swagger/)
* [ReDoc](https://api.kralis.app/schema/redoc/)
* [OpenAPI schema](https://api.kralis.app/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.