Developer access request
Developer API Access
External API clients can register, apply for reviewed access, and integrate safely after approval.
External integration workflow
Register first. Apply next. Integrate after approval.
External systems can request controlled read-only API access to EduSphere training, games, comics and exams. API clients are separate from teachers, students, parents and school staff.
What can be requested
Access is granted by scope, not by open database access.
TrainingApproved learning content and training materials.
GamesApproved learning games without hidden answer keys.
ComicsPublished educational comics and safe reading metadata.
ExamsRestricted exam access. No answer keys are exposed through the API.
How the API access process works
Client account login is now separated from school portal login. The API client dashboard is the home for applications and approved credentials.
1. API client registersThe external organization creates an API client account under the developer portal.
2. API client submits requestOrganization details, purpose, requested modules and expected usage are captured.
3. Admin reviewsThe request stays pending until an authorized admin approves, rejects, or asks for more information.
4. Token is controlledCredentials are scoped, logged, rate-limited and can be suspended or revoked.
Security rule: teachers, students and parents are not API clients. They must use the normal school portal login.