Obtain a Clever district access token either through Clever's Instant Login (user-initiated OAuth) or a district-issued API token for server-to-server sync
GET https://api.clever.com/v3.0/schools to retrieve school records with pagination via the paging.next link in the response
GET /v3.0/sections to retrieve class/section records and note the teacher and student sub-resource links on each section object
GET /v3.0/sections/:id/students to retrieve the student roster for each section
GET /v3.0/users/:id for individual user profile details including name, grade, credentials, and district-assigned identifiers
Store Clever ids alongside your application's user records to enable future delta sync and deprovisioning
Known gotchas
Clever API v3.0 unified the previously separate students/teachers/staff endpoints under /users with a roles field; do not use deprecated v2.1 role-specific endpoints in new integrations
District data access tokens are scoped to a single district; an application serving multiple districts must manage separate tokens per district
Clever's paging.next cursor-based pagination does not support random-access page jumps; you must walk through pages sequentially
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp