IIT Kharagpur Institutional Digital Repository OpenSearch Interface
OpenSearch 1.1 query interface over the Central Library's Institutional Digital Repository, running DSpace 6.0 self-hosted on the institute's own www.idr.iitkgp.ac.in. Verified live 2026-09-01 — /xmlui/open-search/description.xml returns a 603-byte description document naming LongName "Central Library IIT Kharagpur" and Contact dspace-help@library.iitkgp.ac.in, an institution address on the institution's own domain, and /xmlui/open-search/discover returns an Atom 1.0 feed carrying the opensearch: and dc: namespaces. The repository holds 8,162 items; query, format, start, rpp, sort_by, order and scope were each exercised and confirmed. DSpace is open-source software the institute installs and runs itself, not a vendor tenancy, so the host, the contact, the identifiers and the content are all IIT Kharagpur's — but the software is shared by thousands of deployments, so the OpenAPI stored here is a derived description of THIS deployment's observed behaviour, not a DSpace product contract. Three defects are recorded rather than smoothed over: the host has no TLS listener (https:// fails, idr.iitkgp.ac.in does not resolve), every and in the feed is emitted with the authority http://127.0.0.1, and the handle prefix is the DSpace installation default 123456789, so no item carries a persistent identifier. No OAI-PMH provider, DSpace REST API or SWORD service document is deployed — the nginx front end proxies only /xmlui.
IIT Kharagpur Institutional Digital Repository OpenSearch Interface is one of 5 APIs that Indian Institute of Technology Kharagpur publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 1 JSON Schema definition.
Tagged areas include Research Repository, Institutional Repository, DSpace, OpenSearch, and Atom. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, authentication docs, and 1 JSON Schema.
This API exposes 2 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version 1.1.
Requests are made against a single base URL, http://www.idr.iitkgp.ac.in/xmlui.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.
OpenSearch 1.1 description and query operations. All parameters verified live 2026-09-01.
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Item (8 properties), OpenSearchFeed (8 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Indian Institute of Technology Kharagpur 4
Other APIs Indian Institute of Technology Kharagpur publishes across the network.
This is an independent, third-party profile of IIT Kharagpur Institutional Digital Repository OpenSearch Interface, 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.