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

Preservation Catalog HTTP API

Tracks the preservation state of Stanford Digital Repository objects (moab layout). First-party OpenAPI 3.0.0, Apache 2.0, 7 paths, 8 operations, bearer auth. Servers are preservation-catalog-{env}-01.stanford.edu, which do not resolve in public DNS.

Documentation Provider Profile APIs.io OpenAPI GitHub

Preservation Catalog HTTP 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, Preservation, and Research Data. The published artifact set on APIs.io includes an OpenAPI specification and 1 JSON Schema.

This API exposes 8 operations across 7 paths, organized into 2 resource areas, and defines 9 schemas. It is described by OpenAPI 3.0.0, at version 1.0.0.

Requests are made against 3 base URLs: https://preservation-catalog-{env}-01.stanford.edu, https://preservation-catalog-{env}-01.stanford.edu, https://preservation-catalog-{env}-01.stanford.edu.

8 operations 7 paths 9 schemas 4 GET1 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Servers
https://preservation-catalog-{env}-01.stanford.edu
https://preservation-catalog-{env}-01.stanford.edu
https://preservation-catalog-{env}-01.stanford.edu
Authentication
HTTP Bearer
License
Apache 2.0
Resource Areas
2

Authentication & Security 1

Preservation Catalog HTTP API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 8

Across 7 paths, the API surfaces 8 operations — 4 GET, 1 PATCH, 2 POST, 1 PUT. They span 2 resource areas: catalog, objects. Each is listed below with its method, path, parameters, and response codes.

catalog 3

Add and update Moabs in the catalog

POST
/v1/catalog
Add a new Moab to the catalog for an existing object
body → 201409406500
PUT
/v1/catalog/{druid}
Update a Moab for an existing object in the catalog for a new version
1 param body → 200404406400500
PATCH
/v1/catalog/{druid}
Update a Moab for an existing object in the catalog for a new version
1 param body → 200404406400500
objects 5

Preserved Objects

GET
/v1/objects/{id}
Render a single PreservedObject model as JSON
1 param → 200404
GET
/v1/objects/{id}/validate_moab
Starts a validate moab job, which does a validation of the on disk Moab, without reference to the preservation-catalog basis
2 params → 200400423
GET
/v1/objects/{id}/checksum
Show the checksums and filesizes for a single object
1 param → 200400404
GET
/v1/objects/{id}/file
Returns a specific content, metadata, or manifest file for the object.
4 params → 200400404
POST
/v1/objects/{id}/content_diff
Retrieves Moab::FileInventoryDifference model from comparison of passed contentMetadata.xml with latest (or specified) version in Moab for all files (default) or a specified subset.
1 param body → 200400500

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are ContentDiff (6 properties), CatalogOptions (4 properties), PreservedObject (3 properties), AuditResultsResponse (2 properties). Each schema is shown below with its type and property counts.

Druid
string
Digital Repository Unique Identifier (bare or prefixed)
DruidWithOptionalFormat
string
Digital Repository Unique Identifier (bare or prefixed), with a file extension
CatalogOptions
object
Options for catalog controller endpoint
4 properties 3 required
CatalogOptionsWithDruid
ContentDiff
object
A diff between given and existing content metadata (XML)
6 properties 5 required
ChecksumsForObject
array
A representation of all files and checksums for a single object
PreservedObject
object
A preserved object instance
3 properties 3 required
AuditResult
object
A single audit result
AuditResultsResponse
object
Audit results response
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stanford-preservation-catalog-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
Technical Metadata 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#Preservation#Research Data
← Back to P APIs
API Details
ID
stanford:preservation-catalog-api
Server
https://preservation-catalog-{env}-01.stanford.edu
Docs
https://github.com/sul-dlss/preservation_catalog
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=preservation-catalog-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/preservation-catalog-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 Preservation Catalog HTTP 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.