Star Therapeutics · OpenAPI Overlay 1.0.0

API Evangelist enhancements for the Star Therapeutics Content API

9 actions 9 updates update extends openapi/star-therapeutics-content-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Star Therapeutics's API. It is a proposal applied on top of the contract, not a document Star Therapeutics publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-notex-apievangelist-profilex-apievangelist-harvestedx-apievangelist-contributionx-provider-publishes-openapix-provider-developer-programx-surface-class

Targets 8

$.info
$.paths['/wp/v2/posts'].get
$.paths['/wp/v2/tags'].get
$.paths['/wp/v2/comments'].get
$.paths['/wp/v2/avada_faq'].get
$.paths['/wp/v2/avada_portfolio'].get
$.components.schemas.Post
$.components.schemas.Error

OpenAPI Overlay

star-therapeutics-content-overlay.yaml Raw ↑
# authorship: generated by API Evangelist tooling. Stamped 2026-08-18
# on the file's own generator header (roadmap#64). An unmarked file is
# NOT assumed to be ours -- absence of evidence was never stamped.
x-method: generated
overlay: 1.0.0
info:
  title: API Evangelist enhancements for the Star Therapeutics Content API
  version: 1.0.0
extends: openapi/star-therapeutics-content-openapi.yml
x-generated: '2026-08-05'
x-method: generated
x-source: >-
  Generated by the API Evangelist enrichment pipeline on 2026-08-05. Records the enhancements API
  Evangelist added on top of the raw WordPress route index at
  https://star-therapeutics.com/wp-json/. Star Therapeutics 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 the provider's own contract.
actions:
- target: $.info
  update:
    x-apievangelist-profile: https://apis.io/providers/star-therapeutics/
    x-apievangelist-harvested: '2026-08-05'
    x-apievangelist-contribution: >-
      Operation summaries, descriptions, operationIds, tag groupings, response schemas, pagination
      headers and error responses were authored by API Evangelist. The route paths, HTTP methods
      and every query parameter were taken verbatim from the provider's published route index.
- target: $.info
  update:
    x-provider-publishes-openapi: false
    x-provider-developer-program: false
    x-surface-class: cms-content-api
- target: $.paths['/wp/v2/posts'].get
  update:
    x-apievangelist-note: >-
      This is the company news archive and the highest-value operation on the surface — 28 press
      releases, news-coverage items and scientific presentations from 2022-02-16 to 2026-07-06,
      classified by the five registered categories.
- target: $.paths['/wp/v2/tags'].get
  update:
    x-apievangelist-note: Registered and reachable but empty (X-WP-Total 0) on this deployment.
- target: $.paths['/wp/v2/comments'].get
  update:
    x-apievangelist-note: Registered and reachable but empty (X-WP-Total 0) on this deployment.
- target: $.paths['/wp/v2/avada_faq'].get
  update:
    x-apievangelist-note: >-
      Avada theme custom post type. Registered and reachable but empty (X-WP-Total 0) — modelled so
      the surface is complete, not because it carries data.
- target: $.paths['/wp/v2/avada_portfolio'].get
  update:
    x-apievangelist-note: >-
      Avada theme custom post type. Registered and reachable but empty (X-WP-Total 0) — modelled so
      the surface is complete, not because it carries data.
- target: $.components.schemas.Post
  update:
    x-apievangelist-note: >-
      yoast_head, yoast_head_json, featured_image_src, featured_image_src_square, author_info and
      class_list are deployment-specific extensions added by the Yoast SEO plugin and the Avada
      theme, not part of the upstream wp/v2 Post contract. They were observed on live responses on
      2026-08-05 and may disappear on a plugin or theme change.
- target: $.components.schemas.Error
  update:
    x-apievangelist-note: >-
      The WordPress REST error envelope. Deliberately not remapped to RFC 9457 problem+json — see
      errors/star-therapeutics-problem-types.yml for why no problem-type URIs are invented here.