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
Stanford University

Technical Metadata API

Technical (format, characterization) metadata for Stanford Digital Repository files. First-party OpenAPI 3.0.0, Apache 2.0, 3 paths, 3 operations, 14 component schemas. Declares no security scheme; servers technical-metadata-{env}.stanford.edu do not resolve in public DNS.

Documentation Provider Profile APIs.io OpenAPI GitHub

Technical Metadata API is one of 15 APIs that Stanford University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Digital Repository, Metadata, and Preservation. The published artifact set on APIs.io includes an OpenAPI specification and 1 JSON Schema.

This API exposes 3 operations across 3 paths, and defines 14 schemas. It is described by OpenAPI 3.0.0, at version 1.0.0.

Requests are made against 2 base URLs: https://technical-metadata-{env}.stanford.edu, https://technical-metadata-{env}.stanford.edu.

3 operations 3 paths 14 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Servers
https://technical-metadata-{env}.stanford.edu
https://technical-metadata-{env}.stanford.edu
License
Apache 2.0
Resource Areas
1

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

metadata 3

Digital Repository Objects

POST
/v1/technical-metadata
Create the metadata for the object
technical_metadata#create body → 200
GET
/v1/technical-metadata/druid/{druid}
Get the metadata for the files associated with a druid
technical_metadata#show_by_druid 1 param → 200404
POST
/v1/technical-metadata/audit/{druid}
Diff the technical metadata DB entries for a druid against the expected file/hash list provided to the endpoint
technical_metadata#audit_by_druid 1 param body → 200404401

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are VideoMetadata (13 properties), PdfMetadata (10 properties), AvMetadata (10 properties), DroFile (10 properties). Each schema is shown below with its type and property counts.

AudioMetadata
object
Audio-specific technical metadata
8 properties
AvMetadata
object
Audio/visual-specific technical metadata
10 properties
DroFile
object
Technical metadata for a single file
10 properties 2 required
DroFilePart
object
Technical metadata for part of a file, e.g., a track
7 properties 1 required
Druid
string
Digital Repository Unique Identifier (ID)
FileURI
string
File URI for the absolute path of the file
FileName
string
filename for a file in SDR (from Cocina metadata)
FileInfo
object
Information about a file.
2 properties 2 required
FileAuditInfo
object
Information about a file in SDR for which we expect technical metadata to exist.
2 properties 2 required
FileAuditResult
object
Information about detected differences between expected technical metadata entries and actual technical metadata entries
3 properties
ImageMetadata
object
Image-specific technical metadata
2 properties
OtherAvMetadata
object
Other technical metadata for a file part
2 properties
PdfMetadata
object
PDF-specific technical metadata
10 properties
VideoMetadata
object
Video-specific technical metadata
13 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stanford-technical-metadata-api-openapi.yml Raw ↑

Other APIs Stanford University publishes across the network.

Stanford Libraries PURL API
AE Profile APIs.io
Stanford Libraries IIIF API
AE Profile APIs.io
Stanford Libraries Library Hours API
AE Profile APIs.io
Stanford Libraries Digital Stacks API
AE Profile APIs.io
Stanford Libraries Embed API
AE Profile APIs.io
SDR API
AE Profile APIs.io
DOR Services API
AE Profile APIs.io
Preservation Catalog HTTP API
AE Profile APIs.io
SURI API
AE Profile APIs.io
ExploreCourses course-data XML query interface
AE Profile APIs.io
Stanford Identity Provider — SAML 2.0 metadata
AE Profile APIs.io
Stanford AI API Gateway
AE Profile APIs.io
#Digital Repository#Metadata#Preservation
← Back to T APIs
API Details
ID
stanford:technical-metadata-api
Server
https://technical-metadata-{env}.stanford.edu
Docs
https://github.com/sul-dlss/technical-metadata-service
Provider
Stanford University
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=technical-metadata-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/technical-metadata-api"

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 Technical Metadata 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.