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 Academic Assets Archives Portal API

The one surface where the University of Tokyo publishes actual API documentation — at /portal/help/api, in Japanese only. It names a search API described as OpenSearch and a harvesting API described as OAI-PMH, and alongside them the portal serves item representations as JSON-LD (application/ld+json, DC-NDL vocabulary), CSV and refer/BibIX through a _format parameter. The search endpoint itself returns HTTP 403 to external automated clients even though its OpenSearch description document is served at 200; the item representations and manifests are open.

Documentation Provider Profile APIs.io OpenAPI GitHub

UTokyo Academic Assets Archives Portal API is one of 5 APIs that University of Tokyo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Digital Archives, Library, Metadata, Open Access, and JSON-LD. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a JSON-LD context.

This API exposes 6 operations across 6 paths, organized into 3 resource areas. It is described by OpenAPI 3.1.0, at version 2026-08-19.

Requests are made against 2 base URLs: https://da.dl.itc.u-tokyo.ac.jp/portal, https://iiif.dl.itc.u-tokyo.ac.jp.

6 operations 6 paths 0 schemas 6 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://da.dl.itc.u-tokyo.ac.jp/portal
Contact
University of Tokyo Library System — Archives Portal
License
Reuse conditions of the General Library, The University of Tokyo
Resource Areas
3

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 6 GET. They span 3 resource areas: search, items, iiif. Each is listed below with its method, path, parameters, and response codes.

search 2

OpenSearch-described search over the portal.

GET
/opensearch.xml
OpenSearch description document
getOpenSearchDescription → 200
GET
/search
Search the portal (documented; blocked to external automated clients)
searchAssets 10 params → 200403
items 1

Item representations in JSON-LD, CSV and refer/BibIX.

GET
/assets/{assetId}
Retrieve one archival item
getAsset 2 params → 200404
iiif 3

IIIF Presentation and Image API endpoints.

GET
/repo/iiif/{assetId}/manifest
IIIF Presentation manifest for an item
getIiifManifest 1 param → 200
GET
/iiif/2/{identifier}/info.json
IIIF Image API image information
getIiifImageInfo 1 param → 200
GET
/iiif/2/{identifier}/{region}/{size}/{rotation}/{quality}.{format}
IIIF Image API image request
getIiifImage 6 params → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-tokyo-archives-portal-openapi.yml Raw ↑

Other APIs University of Tokyo publishes across the network.

UTokyo IIIF Presentation and Image APIs
AE Profile APIs.io
UTokyo OAI-PMH Metadata Harvesting
AE Profile APIs.io
UTokyo Repository Records API
AE Profile APIs.io
UTokyo Identity Federation (GakuNin SAML 2.0)
AE Profile APIs.io
#Digital Archives#Library#Metadata#Open Access#JSON-LD#OpenSearch#IIIF
← Back to U APIs
API Details
ID
university-of-tokyo:archives-portal
Base URL
https://da.dl.itc.u-tokyo.ac.jp/portal
Docs
https://da.dl.itc.u-tokyo.ac.jp/portal/help/api
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=archives-portal&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/archives-portal"

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 Academic Assets Archives Portal 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.