API archive entry · source-reported
Harvard Art Museums
Art
From the publisher
README & documentation
Source previewRead the project’s overview, installation instructions and usage examples. The original README is the source of truth.
The Harvard Art Museums API is a REST-style service designed for developers who wish to explore and integrate the museums’ collections in their projects. The API provides direct access to the data that powers the museums' website and many other aspects of the museums. All requests to the API begin with: And all requests must also specify the resource you want to retrieve: And every request must be accompanied by the apikey parameter and an API key. The API uses keys to authenticate requests. API keys take the form 00000000-0000-0000-0000-000000000000. Here is the full structure of a typical request: Send a request to obtain your key. All data is in JSON format. Here is a typical response: Requests that return large numbers of records will be spread across multiple pages. By default, a request returns 10 records per page. You can increase this number (up to 100) by adding the…
Read the full README ↗ · Preview checked 2026-10-28T22:34:41.458Z
Inside the original README — Document outline
- Harvard Art Museums API Documentation
- Access to the API
- Responses and data format
- Paging through data
- Errors
- Images
- Analysis
- Resources that are available
- Experimental data
- Learning the API
- Introduction to APIs
- Example projects
Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.
Links from the README
References supplied by the publisher, not independently verified endorsements. Check the destination before downloading files or entering credentials.
Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.
Where these facts came from
AltAPIs imported it from public-apis/public-apis. The source link and dates remain visible for independent inspection.
What is reported
- Name, category, and short description
- Authentication label
- HTTPS and CORS labels
- Provider/source URL
What is not established
- Current uptime or availability
- Pricing, quotas, and rate limits
- Security, compliance, or licensing posture
- SDK quality or endpoint completeness
Record checkpoints
- First observed: Sep 14, 2026
- Last directory-field change: Sep 14, 2026
- Current source observation: Oct 30, 2026
Source reference
This page separates source-reported facts from questions that need live provider verification.