Leo1
LEO1 is a Mumbai-based education fintech founded in 2017 that operates an all-in-one campus and financial platform for Indian educational institutions. The company issues co-branded student and alumni prepaid cards, collects and reconciles institutional fees, and originates fee-financing (education loan) journeys that convert lump-sum tuition into instalments while giving institutes regularized cash flow. LEO1 exposes the LEO1 Fees SDK — a documented server-to-server and web checkout integration that lets an institute ERP start a fee transaction, embed the hosted checkout, and receive payment-gateway and fee-finance webhook notifications — backed by a public OpenAPI 3.0.2 description covering student, fee-due, fee-collection, payment, NACH/eNACH mandate, refund, penalty, waiver, settlement and institute administration operations. Backed by QED Investors, LEO1 reports partnerships with 31+ institution groups serving over half a million students across India.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Leo1 the way a machine reads it — 68 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Leo1 scores 41.3/100 (developing), with a separate agent-readiness read of 28/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Leo1's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/leo1/"
title="Leo1 on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/leo1.svg"
alt="Leo1 Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/leo1/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/leo1/"
title="Leo1 on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/leo1/card.svg"
alt="Leo1 Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Leo1
Each block below is one kind of artifact we hold for Leo1. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 32
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Leo1 api API
General system endpoints for the API.
Leo1 auth API
The auth API from Leo1 — 4 operation(s) for auth.
Leo1 Common Fee Type API
The Common Fee Type API from Leo1 — 1 operation(s) for common fee type.
Leo1 Communication API
The Communication API from Leo1 — 3 operation(s) for communication.
Leo1 documents API
The documents API from Leo1 — 4 operation(s) for documents.
Leo1 Enach API
The Enach API from Leo1 — 4 operation(s) for enach.
Leo1 fee_collections API
The fee_collections API from Leo1 — 7 operation(s) for fee_collections.
Leo1 fee_dues API
The fee_dues API from Leo1 — 2 operation(s) for fee_dues.
Leo1 institute API
The institute API from Leo1 — 3 operation(s) for institute.
Leo1 Institute Course API
The Institute Course API from Leo1 — 2 operation(s) for institute course.
Leo1 Institute Course Class API
The Institute Course Class API from Leo1 — 3 operation(s) for institute course class.
Leo1 Institute Course Class Fee Structure Mapping API
The Institute Course Class Fee Structure Mapping API from Leo1 — 7 operation(s) for institute course class fee structure mapping.
Leo1 Institute Course Fee Structure API
The Institute Course Fee Structure API from Leo1 — 4 operation(s) for institute course fee structure.
Leo1 Institute Fee Type API
The Institute Fee Type API from Leo1 — 2 operation(s) for institute fee type.
Leo1 Institute Payment API
The Institute Payment API from Leo1 — 5 operation(s) for institute payment.
Leo1 Nach Feature API
The Nach Feature API from Leo1 — 30 operation(s) for nach feature.
Leo1 Nach Feature V2 API
The Nach Feature V2 API from Leo1 — 1 operation(s) for nach feature v2.
Leo1 Operations API
The Operations API from Leo1 — 2 operation(s) for operations.
Leo1 payment API
The payment API from Leo1 — 12 operation(s) for payment.
Leo1 penalty API
The penalty API from Leo1 — 1 operation(s) for penalty.
Leo1 refund API
The refund API from Leo1 — 1 operation(s) for refund.
Leo1 Reversal Feature API
The Reversal Feature API from Leo1 — 2 operation(s) for reversal feature.
Leo1 SDK API
The SDK API from Leo1 — 5 operation(s) for sdk.
Leo1 student account API
The student account API from Leo1 — 4 operation(s) for student account.
Leo1 student API
The student API from Leo1 — 13 operation(s) for student.
Leo1 student coin request API
The student coin request API from Leo1 — 3 operation(s) for student coin request.
Leo1 student otp API
The student otp API from Leo1 — 3 operation(s) for student otp.
Leo1 Summary for fee module API
The Summary for fee module API from Leo1 — 5 operation(s) for summary for fee module.
Leo1 Switch Feature API
The Switch Feature API from Leo1 — 2 operation(s) for switch feature.
Leo1 transactions API
The transactions API from Leo1 — 10 operation(s) for transactions.
Leo1 user API
The user API from Leo1 — 2 operation(s) for user.
Leo1 waiver API
The waiver API from Leo1 — 1 operation(s) for waiver.
Scroll within the panel for all 32 ·
Open Collections 33
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONleofees_backend api API
OPEN COLLECTIONleofees_backend api auth API
OPEN COLLECTIONleofees_backend api Common Fee Type API
OPEN COLLECTIONleofees_backend api Communication API
OPEN COLLECTIONleofees_backend api documents API
OPEN COLLECTIONleofees_backend api Enach API
OPEN COLLECTIONleofees_backend api fee_collections API
OPEN COLLECTIONleofees_backend api fee_dues API
OPEN COLLECTIONleofees_backend api institute API
OPEN COLLECTIONleofees_backend api Institute Course API
OPEN COLLECTIONleofees_backend api Institute Course Class API
OPEN COLLECTIONleofees_backend api Institute Course Fee Structure API
OPEN COLLECTIONleofees_backend api Institute Fee Type API
OPEN COLLECTIONleofees_backend api Institute Payment API
OPEN COLLECTIONleofees_backend api Nach Feature API
OPEN COLLECTIONleofees_backend api Nach Feature V2 API
OPEN COLLECTIONleofees_backend api Operations API
OPEN COLLECTIONleofees_backend api payment API
OPEN COLLECTIONleofees_backend api penalty API
OPEN COLLECTIONleofees_backend api refund API
OPEN COLLECTIONleofees_backend api Reversal Feature API
OPEN COLLECTIONleofees_backend api SDK API
OPEN COLLECTIONleofees_backend api student account API
OPEN COLLECTIONleofees_backend api student API
OPEN COLLECTIONleofees_backend api student coin request API
OPEN COLLECTIONleofees_backend api student otp API
OPEN COLLECTIONleofees_backend api Summary for fee module API
OPEN COLLECTIONleofees_backend api Switch Feature API
OPEN COLLECTIONleofees_backend api transactions API
OPEN COLLECTIONleofees_backend api user API
OPEN COLLECTIONleofees_backend api waiver API
OPEN COLLECTIONScroll within the panel for all 33 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Leo1 Fees Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Leo1 — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/leo1 · machine-readable index on apis.io
This is an independent, third-party profile of Leo1, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.