# authorship: generated by API Evangelist tooling. x-method: generated overlay: 1.0.0 info: title: API Evangelist enhancements for the LEAF4Life content API version: 1.0.0 extends: openapi/leaf4life-pages-api-openapi.yml x-extends-all: - openapi/leaf4life-pages-api-openapi.yml - openapi/leaf4life-media-api-openapi.yml - openapi/leaf4life-taxonomy-api-openapi.yml - openapi/leaf4life-discovery-api-openapi.yml - openapi/leaf4life-search-api-openapi.yml - openapi/leaf4life-users-api-openapi.yml - openapi/leaf4life-posts-api-openapi.yml - openapi/leaf4life-oembed-api-openapi.yml x-generated: '2026-08-25' x-source: >- Generated by the API Evangelist enrichment pipeline on 2026-08-25. Records the enhancements API Evangelist added on top of the raw WordPress route index at https://leafforlife.com/wp-json/. LEAF4Life publishes no OpenAPI, so there is no provider-authored original to mutate — this overlay documents what we contributed, so the derivation stays auditable and separable from anything the provider actually publishes. actions: - target: $.info update: x-apievangelist-profile: https://apis.io/providers/leaf4life/ x-apievangelist-harvested: '2026-08-25' x-apievangelist-contribution: >- Operation summaries, descriptions, operationIds, tag groupings, response schemas, pagination response headers and the shared error responses were authored by API Evangelist. The route paths, HTTP methods and every single query parameter — including enums, defaults, minima and maxima — were taken verbatim from the provider's own published route index. - target: $.info update: x-provider-publishes-openapi: false x-provider-developer-program: false x-surface-class: cms-content-api x-company-sector: biopharmaceutical - target: $.paths['/wp/v2/pages'].get update: x-apievangelist-note: >- The highest-value operation on the surface, and the one with the sharpest caveat. It enumerates the entire public website — 8 pages — but content.rendered and excerpt.rendered are empty on every one of them, because the theme template `template-modular.php` stores page bodies in page-builder postmeta rather than post_content. Treat this as an index of what exists and when it changed, not as a content source. - target: $.paths['/wp/v2/search'].get update: x-apievangelist-note: >- Live and correct, and returns zero for every site term — a direct consequence of the empty post_content recorded on /wp/v2/pages. Verified against ?search=hypoxia, ?search=hypoxia&subtype=page and /wp/v2/pages?search=hypoxia on 2026-08-25, all X-WP-Total: 0. - target: $.paths['/wp/v2/tags'].get update: x-apievangelist-note: >- 21 terms, all with count 0, and the slugs are theme-demo residue (animation, beard, camera, sandwich, watch). Do not mine this route as a company vocabulary. - target: $.paths['/wp/v2/posts'].get update: x-apievangelist-note: >- Registered, reachable and empty (X-WP-Total 0). LEAF4Life publishes no news archive or press feed through WordPress, so /feed/ carries no items either. - target: $.paths['/wp/v2/media'].get update: x-apievangelist-note: >- 59 image attachments, all PNG or JPEG, 2020-09-22 to 2026-07-05. No PDFs, posters, protocols or datasets — none of the company's scientific material is published as a downloadable asset here.