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

T2R2 Research Repository OAI-PMH

OAI-PMH 2.0 metadata harvesting interface for T2R2, the Science Tokyo / Tokyo Tech Research Repository, operated by the university library on the institution's own host. Repository name "T2R2 -Tokyo Tech Research Repository-", protocol version 2.0, earliest datestamp 2008-05-01, metadata prefixes oai_dc and junii2, gzip and deflate compression, no set hierarchy. No signup, no key, no rate limits. Verified live on 2026-08-30 across Identify, ListMetadataFormats, ListIdentifiers, ListSets and two error paths. SUNSET: the operator's notice of 2026-07-22 ended T2R2 search on 2026-08-20 and ends registration on 2026-10-01 — re-probe before relying on this endpoint.

T2R2 Research Repository OAI-PMH is one of 4 APIs that Tokyo Institute of Technology publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Repository, OAI-PMH, Research, Open Access, and Metadata. The published artifact set on APIs.io includes API documentation and an OpenAPI specification.

This API exposes 1 operation across 1 path, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version 2.0.

Requests are made against a single base URL, https://t2r2.star.titech.ac.jp/oaipmh.

1 operations 1 paths 3 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.0
Base URL
https://t2r2.star.titech.ac.jp/oaipmh/OAIHandler
License
Not stated by the operator
Resource Areas
1

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

OAI-PMH 1

OAI-PMH 2.0 protocol verbs. All six verbs are dispatched from a single path via the verb query parameter.

GET
/OAIHandler
OAI-PMH 2.0 request dispatcher
oaipmh 7 params → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Identify (8 properties), OAIPMHResponse (4 properties), OAIPMHError (2 properties). Each schema is shown below with its type and property counts.

OAIPMHResponse
object
XML document rooted at {http://www.openarchives.org/OAI/2.0/}OAI-PMH. Modelled here as an object because OpenAPI has no native XSD import; the authoritative sc…
4 properties
Identify
object
Values below are the live values observed on 2026-08-30, not placeholders.
8 properties
OAIPMHError
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tokyo-institute-of-technology-t2r2-oaipmh-openapi.yml Raw ↑

Other APIs Tokyo Institute of Technology publishes across the network.

GakuNin Shibboleth Identity Provider (SAML 2.0)
Science Tokyo Repository OAI-PMH (JAIRO Cloud tenant)
EX-TIC GakuNin SAML entity (tenant)
Where this information came from

This is an independent, third-party profile of T2R2 Research Repository OAI-PMH, 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.