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

University of Tokyo Records API

Deposited items — theses, journal articles, departmental bulletins, research data.

University of Tokyo Records API is one of 6 APIs that University of Tokyo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Records. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a JSON-LD context, authentication docs, and 1 JSON Schema.

This API exposes 2 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 2026-08-19.

Requests are made against a single base URL, https://repository.dl.itc.u-tokyo.ac.jp/api.

2 operations 2 paths 3 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026-08-19
Base URL
https://da.dl.itc.u-tokyo.ac.jp/portal
Resource Areas
1

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.

records 2

Deposited items — theses, journal articles, departmental bulletins, research data.

GET
/records/
Search and page through repository records
listRecords 4 params → 200500
GET
/records/{recordId}
Retrieve one record by its control number
getRecord 1 param → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are RecordMetadata (21 properties), Record (5 properties), RecordList (3 properties). Each schema is shown below with its type and property counts.

RecordMetadata
object
JPCOAR-shaped item metadata. itemmetadata carries the raw WEKO item-type attribute map with Japanese attributename labels and opaque item keys; the sibling top…
21 properties
Record
object
5 properties 5 required
RecordList
object
Paged envelope. Observed on every 200 from /records/.
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-tokyo-records-api-openapi.yml Raw ↑

Other APIs University of Tokyo publishes across the network.

UTokyo Identity Federation (GakuNin SAML 2.0)
University of Tokyo Iiif API
University of Tokyo Items API
University of Tokyo Oai Pmh API
University of Tokyo Search API
Where this information came from

This is an independent, third-party profile of University of Tokyo Records 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.