Education Data Developer Portal

Build with secure, scalable access to schools, students, attendance, and behavioural data. REST, GraphQL, and AI-ready MCP endpoints — all behind one consistent gateway.


Three APIs, one platform

Pick the API style that fits how you build. All three share the same data model, authentication, and rate limits.

REST

Traditional REST endpoints for aggregate statistics — attendance summaries, incident breakdowns, and school-level metrics. Ideal for dashboards, scheduled reports, and partner integrations.

GraphQL

Relay-style GraphQL for flexible, query-driven access to schools, students, attendance, and incidents. Cursor pagination, filtering, and cost-aware rate limiting built in.

MCP

Model Context Protocol interface for AI agents — Claude, Cursor, and custom LLM clients. Exposes the same data as the REST API through standard tool calls.


Why integrate with us

Built for partners who need predictable performance, clear rate limits, and full visibility into the integration lifecycle.

Secure by default

OAuth 2.0 with JWT, signed by the identity provider and validated at the gateway. School-level authorisation enforced at the API layer — your application only sees what you're approved to access.

Predictable limits

Tier-based rate limits (free/standard/premium) with per-school sub-limits and GraphQL cost analysis. Headers tell you exactly how much budget you have left so you can pace your integration sensibly.

Designed for AI

First-class Model Context Protocol support means AI agents — including Claude Desktop, Cursor, and custom LLM clients — can call our APIs through standard MCP tool conventions, with the same auth and limits as REST.


Get up and running in minutes

Four steps from registration to your first call. No backend changes required, no SDK installation, no waiting for approval.

  1. Register

Create an application in the portal. Pick a tier. Get your client credentials.

  1. Authenticate

Exchange credentials for an access token via OAuth 2.0 client credentials.

  1. Try

Test your token live in the portal's Try-It-Out console — no client code needed.

  1. Build

Plug it into your application. Use the OAS to generate SDKs in your language.

Ready to start?

Browse the API catalog, read the integration guides, or jump straight to creating your first application.