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

DAMS API — UC Davis Library Digital Collections

The Digital Asset Management System API behind digital.ucdavis.edu, built on 'fin', the UC Davis Library's own open-source repository framework (github.com/ucd-library/fin). OpenAPI 3.0.0, MIT licensed, contact UC Davis Library Online Strategy, four documented paths over collections and items. Verified live on 2026-08-19, but honestly: it is only partly usable anonymously — /api/collection returns HTTP 200 carrying an Elasticsearch parse error and a Node.js stack trace, and item lookups return HTTP 200 with a body of null on a miss. Recorded with those defects rather than presented as clean.

DAMS API — UC Davis Library Digital Collections is one of 18 APIs that University of California, Davis publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Digital Collections, Library, Repository, and Open-Source. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 6 operations across 4 paths, organized into 3 resource areas. It is described by OpenAPI 3.0.0, at version 1.0.0.

Requests are made against a single base URL, https://digital.ucdavis.edu.

6 operations 4 paths 0 schemas 4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Base URL
https://digital.ucdavis.edu
Resource Areas
3

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 4 GET, 2 POST. They span 3 resource areas: collection, item, page search. Each is listed below with its method, path, parameters, and response codes.

collection 3
GET
/api/collection/{collectionId}
Get collection information by id
1 param → 200
POST
/api/collection/{collectionId}
Search for collections by keyword
1 param body → 200
GET
/api/collection/edits/collection/{collectionId}
Find item and collection edits for a collection by id
1 param → 200
item 2
GET
/api/item/{itemId}
Get item information by id
1 param → 200
POST
/api/item/{itemId}
Search for items by keyword
1 param body → 200
page search 1
GET
/api/page-search/ia
Search item by keyword
2 params → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uc-davis-dams-api-openapi.yml Raw ↑

Other APIs University of California, Davis publishes across the network.

Aggie Experts API
UC Davis Shibboleth Identity Provider (SAML 2.0 / InCommon)
UC Davis Health FHIR R4 endpoint
IET Middleware Web Service APIs
UC Davis Health Systems Integration APIs
CAES ACE API
PEAKS (CAES) — Access API
PEAKS (CAES) — Documents API
PEAKS (CAES) — Equipment API
PEAKS (CAES) — Keys API
PEAKS (CAES) — KeySerials API
PEAKS (CAES) — People API
Where this information came from

This is an independent, third-party profile of DAMS API — UC Davis Library Digital Collections, 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.