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

ODNI Public Content API

The anonymous, read-only WordPress REST API behind www.odni.gov. Serves ODNI newsroom posts (press releases, remarks, interviews and reports), the site's structural pages, the media library, and the Download Monitor catalog of published ODNI documents. DERIVED description — ODNI publishes no specification; the OpenAPI here was derived from the live route discovery document and every operation was confirmed 200 anonymously on 2026-09-06. The canonical /wp-json/ root is 301'd to the homepage by the site's Akamai edge, so the API is reachable only through the query-string route form https://www.odni.gov/?rest_route=/... . Content only — no intelligence holdings are exposed.

ODNI Public Content API is published by Director of National Intelligence on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include News, Publications, Content, Government, and Transparency. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 24 operations across 24 paths, organized into 7 resource areas, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version wp/v2.

Requests are made against 2 base URLs: https://www.odni.gov/wp-json, https://www.odni.gov/?rest_route=.

24 operations 24 paths 3 schemas 24 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
wp/v2
Base URL
https://www.odni.gov/?rest_route=/
Resource Areas
7

Paths & Operations 24

Across 24 paths, the API surfaces 24 operations — 24 GET. They span 7 resource areas: News, Pages, Publications, Taxonomy, Media, Search, Discovery. Each is listed below with its method, path, parameters, and response codes.

News 2

ODNI newsroom posts — press releases, remarks, interviews and reports.

GET
/wp/v2/posts
List ODNI news posts
listPosts 25 params → 200400404
GET
/wp/v2/posts/{id}
Retrieve one ODNI news post
getPost 1 param → 200400404
Pages 2

Structural site pages.

GET
/wp/v2/pages
List ODNI site pages
listPages 19 params → 200400404
GET
/wp/v2/pages/{id}
Retrieve one ODNI site page
getPage 1 param → 200400404
Publications 2

The Download Monitor catalog of published ODNI documents.

GET
/wp/v2/dlm_download
List ODNI publications and downloads
listDownloads 20 params → 200400404
GET
/wp/v2/dlm_download/{id}
Retrieve one ODNI publication
getDownload 1 param → 200400404
Taxonomy 6

Categories and tags classifying news and publications.

GET
/wp/v2/dlm_download_category
List publication categories
listDownloadCategories 10 params → 200400404
GET
/wp/v2/dlm_download_category/{id}
Retrieve one publication category
getDownloadCategory 1 param → 200400404
GET
/wp/v2/dlm_download_tag
List publication tags
listDownloadTags 11 params → 200400404
GET
/wp/v2/categories
List newsroom categories
listCategories 10 params → 200400404
GET
/wp/v2/categories/{id}
Retrieve one newsroom category
getCategory 1 param → 200400404
GET
/wp/v2/tags
List newsroom tags
listTags 11 params → 200400404
Media 2

Media library uploads.

GET
/wp/v2/media
List media library items
listMedia 20 params → 200400404
GET
/wp/v2/media/{id}
Retrieve one media item
getMedia 1 param → 200400404
Search 1

Cross-type site search.

GET
/wp/v2/search
Search ODNI content
search 7 params → 200400404
Discovery 9

Content types, taxonomies, statuses, authors and oEmbed.

GET
/wp/v2/types
List content types
listTypes 1 param → 200400404
GET
/wp/v2/types/{type}
Retrieve one content type
getType 1 param → 200400404
GET
/wp/v2/taxonomies
List taxonomies
listTaxonomies 1 param → 200400404
GET
/wp/v2/taxonomies/{taxonomy}
Retrieve one taxonomy
getTaxonomy 1 param → 200400404
GET
/wp/v2/statuses
List post statuses
listStatuses 1 param → 200400404
GET
/wp/v2/users
List content authors
listAuthors 14 params → 200400404
GET
/wp/v2/users/{id}
Retrieve one author
getAuthor 1 param → 200400404
GET
/wp/v2/comments
List comments
listComments 17 params → 200400404
GET
/oembed/1.0/embed
oEmbed representation of an ODNI URL
oembed 3 params → 200400404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed is WPError (3 properties). Each schema is shown below with its type and property counts.

WPCollection
array
A page of WordPress REST records. Page size is controlled by perpage (1-100, default 10) and page; the total count and page count are returned in the X-WP-Tota…
WPObject
object
A single WordPress REST record.
WPError
object
The WordPress REST error envelope. This API does NOT use RFC 9457 application/problem+json; errors are returned as application/json with this shape.
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

director-of-national-intelligence-wp-content-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of ODNI Public Content 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.