clever.com
Clever provides school software integrations for rostering, identity, and single sign-on between applications and K–12 districts. It connects partner applications to district data, user identity, and LMS-related workflows.
Clever exposes HTTP integration surfaces for its Data API and OIDC `/userinfo` endpoint, authenticated with district-app bearer tokens or user SSO OAuth bearer tokens depending on the flow.
- Clever Data APIdiscovered
- Clever OIDC UserInfo endpointdiscovered
Have a district authorize your Clever application; Clever creates a district-app token each time a district authorizes the app. Obtain it through the district onboarding flow referenced in Onboarding and Syncing with Clever from the Clever API Overview. This token is used for district-managed API access.
Create a Clever app in the Clever App Dashboard, then send users through Clever's OAuth authorization-code flow as documented in OAuth Implementation. Exchange the authorization code at https://clever.com/oauth/tokens using your app credentials to receive a bearer access_token. For Clever Library testing, the same flow is shown in Testing Clever Library with Postman.
conventions · 1/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✓https://clever.com/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing