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

Indian Institute of Technology Bombay Calendar API

The calendar API from Indian Institute of Technology Bombay — 11 operation(s) for calendar.

Indian Institute of Technology Bombay Calendar API is one of 54 APIs that Indian Institute of Technology Bombay publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Calendar. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, authentication docs, a support channel, and 1 JSON Schema.

This API exposes 27 operations across 11 paths. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://gymkhana.iitb.ac.in/instiapp/api.

27 operations 11 paths 0 schemas 4 DELETE7 GET9 PATCH7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://gymkhana.iitb.ac.in/instiapp/api
Authentication
HTTP Basic
License
AGPLv3
Terms of Service
Resource Areas
1

Authentication & Security 1

Indian Institute of Technology Bombay Calendar API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (Basic). By default, every request must be authenticated.

Paths & Operations 27

Across 11 paths, the API surfaces 27 operations — 4 DELETE, 7 GET, 9 PATCH, 7 POST. Each is listed below with its method, path, parameters, and response codes.

Calendar 27
GET
/calendar/feed/
Calendar feed list
calendar_feed_list → 200
GET
/calendar/preferences/
Calendar preferences list
calendar_preferences_list → 200
PATCH
/calendar/preferences/
Calendar preferences partial update
calendar_preferences_partial_update → 200
GET
/calendar/preferences/bodies/
Calendar preferences bodies list
calendar_preferences_bodies_list → 200
PATCH
/calendar/preferences/bodies/{body_id}/
Calendar preferences bodies partial update
calendar_preferences_bodies_partial_update 1 param → 200
GET
/calendar/shared/
Calendar shared list
calendar_shared_list → 200
POST
/calendar/shared/
Calendar shared create
calendar_shared_create → 201
PATCH
/calendar/shared/
Calendar shared partial update
calendar_shared_partial_update → 200
DELETE
/calendar/shared/
Calendar shared delete
calendar_shared_delete → 204
GET
/calendar/shared/{slug}/
Calendar shared read
calendar_shared_read 1 param → 200
POST
/calendar/shared/{slug}/
Calendar shared create
postCalendarSharedBySlug 1 param → 201
PATCH
/calendar/shared/{slug}/
Calendar shared partial update
patchCalendarSharedBySlug 1 param → 200
DELETE
/calendar/shared/{slug}/
Calendar shared delete
deleteCalendarSharedBySlug 1 param → 204
GET
/calendar/shared/{slug}/events/
Calendar shared events list
calendar_shared_events_list 1 param → 200
POST
/calendar/shared/{slug}/events/
Calendar shared events create
calendar_shared_events_create 1 param → 201
PATCH
/calendar/shared/{slug}/events/
Calendar shared events partial update
calendar_shared_events_partial_update 1 param → 200
DELETE
/calendar/shared/{slug}/events/
Calendar shared events delete
calendar_shared_events_delete 1 param → 204
GET
/calendar/shared/{slug}/events/{event_id}/
Calendar shared events read
calendar_shared_events_read 2 params → 200
POST
/calendar/shared/{slug}/events/{event_id}/
Calendar shared events create
postCalendarSharedBySlugEventsByEventId 2 params → 201
PATCH
/calendar/shared/{slug}/events/{event_id}/
Calendar shared events partial update
patchCalendarSharedBySlugEventsByEventId 2 params → 200
DELETE
/calendar/shared/{slug}/events/{event_id}/
Calendar shared events delete
deleteCalendarSharedBySlugEventsByEventId 2 params → 204
POST
/calendar/shared/{slug}/subscribe/
Calendar shared subscribe create
calendar_shared_subscribe_create 1 param → 201
PATCH
/calendar/shared/{slug}/subscribe/
Calendar shared subscribe partial update
calendar_shared_subscribe_partial_update 1 param → 200
POST
/calendar/shared/{slug}/toggle/
Calendar shared toggle create
calendar_shared_toggle_create 1 param → 201
PATCH
/calendar/shared/{slug}/toggle/
Calendar shared toggle partial update
calendar_shared_toggle_partial_update 1 param → 200
POST
/calendar/shared/{slug}/unsubscribe/
Calendar shared unsubscribe create
calendar_shared_unsubscribe_create 1 param → 201
PATCH
/calendar/shared/{slug}/unsubscribe/
Calendar shared unsubscribe partial update
calendar_shared_unsubscribe_partial_update 1 param → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

iit-bombay-calendar-api-openapi.yml Raw ↑

Other APIs Indian Institute of Technology Bombay publishes across the network.

IITB Central SSO — OpenID Connect
Gymkhana Profiles OAuth API
DSpace Institutional Repository (Central Library)
ITC Single Sign-On
Indian Institute of Technology Bombay Achievements API
Indian Institute of Technology Bombay Achievements Offer API
Indian Institute of Technology Bombay Alumni Login API
Indian Institute of Technology Bombay Alumni Otp Conf API
Indian Institute of Technology Bombay Bans API
Indian Institute of Technology Bombay Bodies API
Indian Institute of Technology Bombay Buy API
Indian Institute of Technology Bombay Check API
Where this information came from

This is an independent, third-party profile of Indian Institute of Technology Bombay Calendar 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.