Welcome to my curated collection of Swagger (OpenAPI 2.0) files, representing a wide range of real-time APIs I have designed and developed over the past 3 years. Each Swagger spec file corresponds to an enterprise-grade backend system integration or microservice, covering diverse domains and operations. This repository serves as a centralized collection of Swagger (OpenAPI Specification 2.0) definitions that I’ve developed for various backend systems. These API specifications are designed following industry best practices and are widely adopted by enterprise applications for seamless integration, consistency, and maintainability.
📝 Each folder corresponds to a real-time project or backend system with its own Swagger (OAS 2.0) file.
- ✅ OpenAPI 2.0 (Swagger) format
- ⚙️ Multiple backend systems (payment gateways, telecoms, logistics, insurance, etc.)
- 📡 Includes RESTful operations:
GET,POST,PUT,DELETE - 🔒 Secure endpoints (OAuth 2.0, JWT, API Keys)
- 📄 Rich documentation for request/response schemas, query parameters, and error codes
- 🌐 Designed for enterprise-grade integrations and middleware systems
| API / Project Name | Description |
|---|---|
| PostProjectAPI_V1 | Accepts project data payloads and integrates with backend systems to create new project records. Used in project lifecycle and tracking systems. |
| GetAccountAPI_V1 | Fetches detailed account information, including user profiles, linked services, and account status. Typically used for authentication and account overview. |
| GetPaymentDetailsAPI_V1 | Fetches Payment related data along with OrderID from Mollie using Payment reference ID. |
| PostSubscriptionAPI_V1 | Submits new subscription requests for a service, supporting telecom and SaaS billing flows. Integrates with external vendor systems for provisioning. |
| UpdateContactInfoAPI_V1 | Updates user contact details (email, phone, address) in the central customer records database, used across CRM and KYC systems. |
This repo serves as a reference portfolio to demonstrate:
- My API design capabilities using OpenAPI/Swagger standards
- Real-world experience in designing scalable and secure REST APIs
- Hands-on work with API-first development, including documentation, versioning, and security
- These Swagger files do not contain any sensitive or client-specific information.
- All identifiers and domains are either generic or anonymized for confidentiality.
If you're interested in discussing any of these APIs, or want to collaborate:
Sai Sheshank Gaddam
📧 gsaisheshank@gmail.com
🔗 https://www.linkedin.com/in/sheshank-gaddam-a32a49168/