← AI resource directorypublic-data-apis

public-data-apis · prepared

Library of Congress JSON/YAML API boundary

Official-source access, API-implemented endpoint selection, response-format, paging, collection-coverage, and interpretation boundaries for the Library of Congress JSON/YAML API.

version 1.0.1freshness currentobserved 2026-09-09T05:21:46Z

resource.public-data.library-of-congress-json-api
sha256:d5999c8c6fb312339bf903fe2c388a4a999695aee74a3baa193a2a11c73fa8d8

Open canonical machine JSON →

Evidence-backed facts

  1. The loc.gov JSON/YAML API provides JSON or YAML structured information for API-implemented loc.gov endpoints, including digitized items, collections, images, and metadata; it does not include Library catalog records. informative
  2. Public reads require no API key or authentication. loc.gov enforces rate limiting without publishing a request-rate value here, and deep paging past the 100,000th search-result item is unsupported; some searches can fail earlier. informative
  3. For a loc.gov page implemented by the API, use ?fo=json or ?fo=yaml; select a documented search, collection, item, or resource endpoint, then narrow searches with documented query parameters. Other loc.gov sections do not provide API responses, and exact parameter or page-size choices remain documentation-dependent. informative
  4. API availability covers only the Library website portions implemented with this API; it does not establish complete holdings coverage, individual-item accuracy, or permission to retrieve or reuse any media. informative