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

Princeton University Art Museum API

Open, REST-style API providing developer access to data about the Princeton University Art Museum and its collections. Four surfaces: objects (with a label-level /tombstone sub-resource and filtering by maker, department, term and on-view status), makers, packages, and a full-text search endpoint that returns the raw Elasticsearch envelope. Pagination and incremental harvesting are supported via size, from, sort, sortorder and lastupdated. No authentication is currently required, though the Museum documents that this may change. Weekly-refreshed static JSON dumps of the whole collection are offered alongside the API for bulk and machine-learning use. The Museum publishes prose documentation, not a contract; the OpenAPI in this repo is DERIVED from that documentation and verified against live responses, and is not Princeton's own artifact.

Princeton University Art Museum API is one of 30 APIs that Princeton University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Museum, Collection, Open Data, IIIF, and JSON. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and 1 JSON Schema.

This API exposes 1 operation across 1 path. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against 2 base URLs: https://allsearch-api.princeton.edu, https://allsearch-api-staging.princeton.edu.

1 operations 1 paths 0 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://data.artmuseum.princeton.edu
Resource Areas
1

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

Art Museum 1
GET
/search/artmuseum
/search/artmuseum?query={query}
searchArtmuseum 1 param → 200400

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

princeton-art-museum-api-openapi.yml Raw ↑

Other APIs Princeton University publishes across the network.

Princeton OIT API Gateway
Princeton University Library Catalog (Orangelight)
PUL Bibliographic Data Web Service (Bibdata)
Figgy Digital Repository — OAI-PMH and IIIF
Princeton Data Commons — Discovery
DataSpace Institutional Repository — OAI-PMH
Princeton University Library Finding Aids (PULFAlight)
Princeton University Library Maps and Geospatial Data (PUL Map)
Digital PUL (DPUL)
Princeton Shibboleth Identity Provider — SAML 2.0 Metadata
Ex Libris Alma / Primo VE — Princeton tenancy (01PRI_INST)
Canvas LMS — Princeton tenancy
Where this information came from

This is an independent, third-party profile of Princeton University Art Museum 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.