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

CPIR Site Metadata API

The anonymously readable metadata layer of the parentcenterhub.org WordPress REST API - the discovery root enumerating 34 namespaces and 717 routes with their argument schemas, the registered content types, taxonomies and publication statuses, and the Yoast SEO head document carrying schema.org JSON-LD for any CPIR URL. Note that the WordPress content collections on this host (posts, pages, media, categories, tags, users, search) are NOT public: every one returns 401 rest_forbidden to an anonymous caller, verified 2026-09-05. Article content is available through the site RSS feed instead.

CPIR Site Metadata API is one of 4 APIs that Center for Parent Information and Resources publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Metadata, Discovery, SEO, and Structured Data. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 5 paths, organized into 3 resource areas, and defines 1 schema. It is described by OpenAPI 3.2.0, at version wp/v2.

Requests are made against a single base URL, https://www.parentcenterhub.org/wp-json.

5 operations 5 paths 1 schemas 5 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
wp/v2
Base URL
https://www.parentcenterhub.org/wp-json
Resource Areas
3

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 5 GET. They span 3 resource areas: Discovery, Metadata, SEO. Each is listed below with its method, path, parameters, and response codes.

Discovery 1

The API root that enumerates every namespace and route on the host.

GET
/
API discovery root
getApiRoot 2 params → 200
Metadata 3

Registered content types, taxonomies and publication statuses.

GET
/wp/v2/types
List registered content types
listContentTypes 1 param → 200
GET
/wp/v2/taxonomies
List registered taxonomies
listTaxonomies 2 params → 200
GET
/wp/v2/statuses
List publication statuses
listPostStatuses 1 param → 200
SEO 1

Yoast SEO head document for a CPIR URL.

GET
/yoast/v1/get_head
Retrieve the SEO head document for a URL
getSeoHead 1 param → 200404

Schemas 1

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

ApiRoot
object
The WordPress REST API index document.
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

center-for-parent-information-and-resources-site-metadata-api-openapi.yml Raw ↑

Other APIs Center for Parent Information and Resources publishes across the network.

CPIR Parent Center Directory API
CPIR Geography Reference API
CPIR oEmbed API
Where this information came from

This is an independent, third-party profile of CPIR Site Metadata 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.