> ## 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.

# API Access, Templates, and Support

> Understand the developer offering, school access, templates, support, and public policy links.

## Developer offering

The Kralis Developer Hub describes the current developer package, API allowance, school-size options, templates, and support benefits. Use the live page for current commercial information rather than copying plan values into a client.

| Resource | What it provides |
| - | - |
| [Developer Hub](https://kralis.app/developers) | Current developer package and FAQs |
| [Contact Sales](https://kralis.app/contact) | School-specific plan and enterprise discussion |
| [Kralis Templates](https://templates.kralis.school) | School website starting points |
| [Support](https://kralis.app/support) | Product and API integration help |

## School and developer relationship

```mermaid theme={null}
flowchart LR
    A[School chooses Kralis] --> B[School is onboarded]
    B --> C[Developer access is confirmed]
    C --> D[School data is configured in Kralis Web]
    D --> E[Developer builds custom client]
    E --> F[Users access Kralis through approved experiences]
```

Developers act for an onboarded school and should use accounts and data approved by that school. A developer arrangement does not permit access to unrelated schools.

The platform support-school switching tools are an internal Kralis operations capability, not a developer integration feature. A custom client should keep one authenticated school context at a time and use `authSchool` for that context. It must never expose a school picker based on guessed acronyms or IDs, or assume that a privileged-looking account can read across schools.

## Templates

Templates can accelerate a school website, but API authentication and private school workflows still require the same security, scoping, pagination, and error handling as any other client.

## Ask support about

* API access or plan questions;
* an operation that is unclear in the live schema;
* approved origins or deployment-specific connectivity;
* a reproducible API failure;
* enterprise school-instance requirements; or
* a planned change that may affect an existing integration.

Include the school, API surface, named operation or REST path, timestamp and timezone, response status, and a sanitized error. Never send credentials or tokens.

## Policies

Using Kralis APIs is subject to the [Terms of Service](https://kralis.app/terms-of-service) and [Privacy Policy](https://kralis.app/privacy-policy).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.