TEGNA Content API (WordPress REST)
The public, unauthenticated read API behind www.tegna.com — TEGNA's corporate and press site. 264 routes across 366 operations serving posts, pages, media, categories, tags, taxonomies, block types, site-health and the WordPress Abilities namespace as JSON, plus oEmbed and AIOSEO metadata. Verified live and callable on 2026-08-13. Reads on public content require no credential; writes require a WordPress Application Password.
TEGNA Content API (WordPress REST) is one of 3 APIs that TEGNA publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Content, Press, WordPress, and Media. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.
This API exposes 366 operations across 264 paths, organized into 5 resource areas, and defines 1 schema. It is described by OpenAPI 3.1.0, at version 2.0.
Requests are made against a single base URL, https://www.tegna.com/wp-json.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
TEGNA Content API (WordPress REST) declares
1 security scheme
for authenticating requests.
It accepts HTTP basic authentication (applicationPassword).
applicationPassword— WordPress Application Passwords (HTTP Basic). The live index advertises the authorization endpoint at https://www.tegna.com/wp-admin/authorize-application.php.…
Paths & Operations 366
Across 264 paths, the API surfaces 366 operations — 37 DELETE, 151 GET, 178 POST. They span 5 resource areas: aioseo/v1, contact-form-7/v1, oembed/1.0, wp-abilities/v1, wp/v2. Each is listed below with its method, path, parameters, and response codes.
WordPress REST namespace aioseo/v1 (137 operations).
WordPress REST namespace contact-form-7/v1 (9 operations).
WordPress REST namespace oembed/1.0 (3 operations).
WordPress REST namespace wp-abilities/v1 (8 operations).
WordPress REST namespace wp/v2 (209 operations).
Schemas 1
The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Error (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from TEGNA 2
Other APIs TEGNA publishes across the network.
This is an independent, third-party profile of TEGNA Content API (WordPress REST), 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.