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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
University of Tokyo

UTokyo Repository Records API

A live, unauthenticated JSON records interface at /api/records/ exposing 69,549 repository records with full-text query, size/page paging and self/next links. Records carry JPCOAR-shaped metadata and a registered DOI under the university's own prefix 10.15083 via JaLC. The university documents this nowhere and its robots.txt disallows /api/, so it is recorded as an internal surface that happens to be reachable rather than as a product — but it is genuinely the institution's, genuinely live, and it is the largest machine-readable corpus the university serves.

Documentation Provider Profile APIs.io OpenAPI GitHub

UTokyo Repository Records API is one of 5 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 Repository, Research Data, Open Access, Metadata, and JPCOAR. The published artifact set on APIs.io includes an OpenAPI specification and 1 JSON Schema.

This API exposes 2 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.1.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.1.0
API Version
2026-08-19
Base URL
https://repository.dl.itc.u-tokyo.ac.jp/api
Contact
University of Tokyo Library System — Digital Library Section
License
Rights vary per record; see the accessRights and rights fields of each record
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.

RecordList
object
Paged envelope. Observed on every 200 from /records/.
3 properties 2 required
Record
object
5 properties 5 required
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

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs University of Tokyo publishes across the network.

UTokyo Academic Assets Archives Portal API
AE Profile APIs.io
UTokyo IIIF Presentation and Image APIs
AE Profile APIs.io
UTokyo OAI-PMH Metadata Harvesting
AE Profile APIs.io
UTokyo Identity Federation (GakuNin SAML 2.0)
AE Profile APIs.io
#Repository#Research Data#Open Access#Metadata#JPCOAR#Theses
← Back to U APIs
API Details
ID
university-of-tokyo:repository-records
Base URL
https://repository.dl.itc.u-tokyo.ac.jp/api
Docs
https://repository.dl.itc.u-tokyo.ac.jp/
Provider
University of Tokyo
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=repository-records&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/repository-records"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of UTokyo Repository 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.