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

Department of Justice CFO Page API

The CFO Page API from Department of Justice — 3 operation(s) for cfo page.

Department of Justice CFO Page API is one of 13 APIs that Department of Justice publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include CFO Page. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 3 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version Versioning not supported.

Requests are made against a single base URL, https://api.foia.gov/api.

3 operations 3 paths 2 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
Versioning not supported
Base URL
https://www.justice.gov/api/v1
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Department of Justice CFO Page API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-Key (APIKeyHeader). By default, every request must be authenticated.

Paths & Operations 3

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

CFO Page 3
GET
/node/cfo_page
List CFO Pages
getNodeCfoPage 4 params → 200400403404
GET
/node/cfo_page/{entity}
Get CFO Page Details
getNodeCfoPageByEntity 1 param → 200400403404
GET
/node/cfo_page/{entity}/field_attachments
CFO Page Attachments
getNodeCfoPageByEntityFieldAttachments 1 param → 200400403404

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are paragraph--attachments (4 properties), node--cfo_page (4 properties). Each schema is shown below with its type and property counts.

node--cfo_page
object
Pages for the Chief FOIA Officers Council. CFO Pages have title, body, and URL slug fields. They are available via a JSON feed.
4 properties 1 required
paragraph--attachments
object
Describes the payload for 'paragraph' entities of the 'attachments' bundle.
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

department-of-justice-cfo-page-api-openapi.yml Raw ↑

Other APIs Department of Justice publishes across the network.

DOJ News API
BJS National Crime Victimization Survey (NCVS) API
BJS NIBRS National Estimates API
FARA e-File Registrant API
DOJ Open Data Catalog
Department of Justice Agency Component API
Department of Justice Agency Taxonomy API
Department of Justice Annual FOIA Report Data API
Department of Justice CFO Committee API
Department of Justice CFO Council API
Department of Justice CFO Meeting API
Department of Justice Quarterly FOIA Report Data API
Where this information came from

This is an independent, third-party profile of Department of Justice CFO Page 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.