How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Leo1 Common Fee Type API

The Common Fee Type API from Leo1 — 1 operation(s) for common fee type.

Leo1 Common Fee Type API is one of 32 APIs that Leo1 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Common Fee Type. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 4 operations across 1 path, and defines 5 schemas. It is described by OpenAPI 3.0.2, at version version.

Requests are made against the base URL https://api.leo1.in.

4 operations 1 paths 5 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.2
API Version
version
Base URL
https://api.leo1.in
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Leo1 Common Fee Type API declares 1 security scheme for authenticating requests. An API key is passed in the header as secret-key (APIKeyHeader).

Paths & Operations 4

Across 1 path, the API surfaces 4 operations — 1 DELETE, 1 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Common Fee Type 4
GET
/api/v1/common_fee_type/
Get Common Fee Types
get_common_fee_types_api_v1_common_fee_type__get 1 param → 200422
PUT
/api/v1/common_fee_type/
Update Common Fee Type
update_common_fee_type_api_v1_common_fee_type__put body → 200422
POST
/api/v1/common_fee_type/
Create Common Fee Type
create_common_fee_type_api_v1_common_fee_type__post body → 200422
DELETE
/api/v1/common_fee_type/
Bulk Delete Common Fee Types
bulk_delete_common_fee_types_api_v1_common_fee_type__delete body → 200422

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are UpdateCommonFeeTypeRequest (3 properties), ValidationError (3 properties), CreateCommonFeeTypeRequest (2 properties), DeleteCommonFeeTypeRequest (1 property). Each schema is shown below with its type and property counts.

ValidationError
object
3 properties 3 required
CreateCommonFeeTypeRequest
object
2 properties 2 required
HTTPValidationError
object
1 property
DeleteCommonFeeTypeRequest
object
1 property 1 required
UpdateCommonFeeTypeRequest
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

leo1-common-fee-type-api-openapi.yml Raw ↑

Other APIs Leo1 publishes across the network.

Leo1 api API
Leo1 auth API
Leo1 Communication API
Leo1 documents API
Leo1 Enach API
Leo1 fee_collections API
Leo1 fee_dues API
Leo1 institute API
Leo1 Institute Course API
Leo1 Institute Course Class API
Leo1 Institute Course Class Fee Structure Mapping API
Leo1 Institute Course Fee Structure API
Where this information came from

This is an independent, third-party profile of Leo1 Common Fee Type API, 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.