Edools
Edools is a Brazilian e-learning and digital-education platform for creating, hosting, and selling online courses, learning paths, and training programs under a white-label school (LMS) with a Netflix-style members area, video hosting, and student engagement tools. The platform is now delivered as HeroSpark (edools.com redirects to herospark.com), a digital-product sales suite for course creators covering checkout, payments (SparkPay), members areas, and a student mobile app. Edools exposes a token-authenticated REST API (base host per-school on myedools.com) for team, content, and student management, plus first-party Ruby and PHP client libraries and theme development tooling, letting integrators sync courses, students, enrollments, and school products with external systems.
Edools publishes 1 API on the APIs.io network. Tagged areas include Company, Education, E-Learning, LMS, and Online Courses.
Edools’ developer surface includes documentation, API reference, support, engineering blog, pricing, signup flow, authentication, and 15 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Edools Core API
Token-authenticated REST API for managing an Edools school — team and role administration, content (courses, learning paths, lessons, media), student management and engagement t...
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API