Project Open Data (data.json) Catalog API

Every U.S. federal executive branch agency is required by the Open Government Data Act of 2018 (and predecessor OMB M-13-13) to publish a public enterprise data inventory as a JSON document at /data.json on its primary domain. The format follows the DCAT-US 1.1 schema (Project Open Data Metadata Schema), an extension of W3C DCAT. Data.gov harvests these /data.json endpoints on a regular cadence and ingests records into the central CKAN catalog. The schema defines a Catalog containing Dataset records with required fields (title, description, keyword, modified, publisher, contactPoint, identifier, accessLevel, bureauCode, programCode) and optional distribution records (downloadURL, accessURL, mediaType, format).

Project Open Data (data.json) Catalog API is one of 4 APIs that Data.gov publishes on the APIs.io network.

This API exposes 1 JSON Schema definition.

Tagged areas include Open Data, DCAT-US, Federal, and Catalog. The published artifact set on APIs.io includes API documentation and 1 JSON Schema.

API entry from apis.yml

apis.yml Raw ↑
aid: data-gov:project-open-data
name: Project Open Data (data.json) Catalog API
tags:
- Open Data
- DCAT-US
- Federal
- Catalog
humanURL: https://resources.data.gov/resources/dcat-us/
properties:
- url: https://resources.data.gov/resources/dcat-us/
  type: Documentation
- url: https://project-open-data.cio.gov/v1.1/schema/
  type: JSONSchema
- url: https://github.com/GSA/project-open-data-dashboard
  type: SourceCode
description: Every U.S. federal executive branch agency is required by the Open Government Data Act of
  2018 (and predecessor OMB M-13-13) to publish a public enterprise data inventory as a JSON document
  at /data.json on its primary domain. The format follows the DCAT-US 1.1 schema (Project Open Data Metadata
  Schema), an extension of W3C DCAT. Data.gov harvests these /data.json endpoints on a regular cadence
  and ingests records into the central CKAN catalog. The schema defines a Catalog containing Dataset records
  with required fields (title, description, keyword, modified, publisher, contactPoint, identifier, accessLevel,
  bureauCode, programCode) and optional distribution records (downloadURL, accessURL, mediaType, format).