openapi: 3.1.0
info:
  title: Daring Foods SEO Metadata API
  version: wp/v2
  summary: Yoast SEO head metadata and schema.org JSON-LD graph for any daring.com URL.
  description: daring.com runs Yoast SEO, which registers a public `yoast/v1` namespace. The `get_head` operation
    resolves any public daring.com URL to that page's rendered SEO head - canonical URL, title, meta description,
    Open Graph and Twitter card properties, and the full schema.org JSON-LD `@graph` Yoast generates for it. For
    an agent this is the most structured description of a Daring recipe or product available from this host, because
    it carries schema.org typing that the content collections themselves do not; the same JSON-LD is also inlined
    on every record returned by the products, recipes, pages and posts collections as `yoast_head_json`. The remaining
    yoast/v1 routes are administrative and return HTTP 401 anonymously.
  contact:
    name: Daring Foods
    url: https://daring.com/faq/
  license:
    name: Site content - all rights reserved; see Terms & Conditions
    url: https://daring.com/terms-and-conditions/
  x-apis-io-provenance:
    method: derived
    source: https://daring.com/wp-json/
    derived_on: '2026-08-04'
    note: Routes enumerated from the live WordPress route index at https://daring.com/wp-json/ (222 routes across
      10 namespaces) on 2026-08-04, then probed anonymously one at a time; only routes verified to return HTTP 200
      without credentials are documented here. Schemas reflect fields observed in the live responses. Write methods
      exist on the same routes but require WordPress authentication (cookie + X-WP-Nonce, or Application Passwords)
      and return HTTP 401 anonymously, so they are not documented. No fabricated operations, parameters or fields.
servers:
- url: https://daring.com/wp-json
  description: Production
tags:
- name: SEO
  description: Yoast SEO head metadata and JSON-LD.
paths:
  /yoast/v1/get_head:
    get:
      tags:
      - SEO
      operationId: getSeoHead
      summary: Retrieve SEO head metadata for a URL
      description: Returns the Yoast SEO head metadata and schema.org JSON-LD graph for a public daring.com URL.
        Verified live (HTTP 200) against the site root.
      parameters:
      - name: url
        in: query
        required: true
        description: The daring.com URL to describe, percent-encoded.
        schema:
          type: string
          format: uri
      responses:
        '200':
          description: SEO head metadata for the requested URL.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/YoastHead'
        '404':
          description: Object not found, or no route matches the request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                code: rest_post_invalid_id
                message: Invalid post ID.
                data:
                  status: 404
components:
  parameters:
    page:
      name: page
      in: query
      description: Current page of the collection (1-based).
      schema:
        type: integer
        minimum: 1
        default: 1
    perPage:
      name: per_page
      in: query
      description: Maximum number of items returned per page. Verified server cap is 100; a larger value returns
        HTTP 400 rest_invalid_param.
      schema:
        type: integer
        minimum: 1
        maximum: 100
        default: 10
    search:
      name: search
      in: query
      description: Limit results to those matching a free-text string.
      schema:
        type: string
    order:
      name: order
      in: query
      description: Sort direction.
      schema:
        type: string
        enum:
        - asc
        - desc
        default: desc
    orderby:
      name: orderby
      in: query
      description: Field to sort the collection by.
      schema:
        type: string
        enum:
        - date
        - id
        - include
        - modified
        - relevance
        - slug
        - title
        default: date
    context:
      name: context
      in: query
      description: Scope under which the request is made; determines the fields present in the response. Anonymous
        callers may use `view` and `embed` only - `edit` returns HTTP 401.
      schema:
        type: string
        enum:
        - view
        - embed
        default: view
    fields:
      name: _fields
      in: query
      description: Comma-separated list of fields to limit the response to (e.g. `id,slug,title,link`). A WordPress
        core response-shaping convention, verified working on this host.
      schema:
        type: string
    embed:
      name: _embed
      in: query
      description: Inline embeddable linked resources (featured media, terms, author) into an `_embedded` object.
      schema:
        type: boolean
    slugFilter:
      name: slug
      in: query
      description: Limit results to items with one of the given slugs.
      schema:
        type: array
        items:
          type: string
    include:
      name: include
      in: query
      description: Limit result set to specific IDs.
      schema:
        type: array
        items:
          type: integer
    exclude:
      name: exclude
      in: query
      description: Ensure result set excludes specific IDs.
      schema:
        type: array
        items:
          type: integer
    offset:
      name: offset
      in: query
      description: Offset the result set by a specific number of items.
      schema:
        type: integer
        minimum: 0
    idPath:
      name: id
      in: path
      required: true
      description: Unique numeric identifier for the object.
      schema:
        type: integer
  headers:
    XWPTotal:
      description: Total number of items in the unpaginated collection.
      schema:
        type: integer
    XWPTotalPages:
      description: Total number of pages available at the requested per_page size.
      schema:
        type: integer
    LinkPagination:
      description: RFC 8288 Link header carrying `prev` and `next` relations for the collection.
      schema:
        type: string
    CacheControl:
      description: 'Observed as `max-age=600, must-revalidate` on this host (WP Engine edge cache, x-cacheable:
        SHORT).'
      schema:
        type: string
  schemas:
    Error:
      type: object
      description: 'The WordPress REST error envelope. NOTE: this is NOT RFC 9457 problem+json - the media type
        is application/json and the shape is {code, message, data}.'
      required:
      - code
      - message
      - data
      properties:
        code:
          type: string
          description: Machine-readable WordPress error code, e.g. rest_post_invalid_id, rest_invalid_param, rest_no_route.
          examples:
          - rest_post_invalid_id
        message:
          type: string
          description: Human-readable error message.
          examples:
          - Invalid post ID.
        data:
          type: object
          properties:
            status:
              type: integer
              description: HTTP status code, repeated in the body.
              examples:
              - 404
            params:
              type: object
              additionalProperties:
                type: string
              description: 'Present on rest_invalid_param: per-parameter validation messages.'
            details:
              type: object
              description: 'Present on rest_invalid_param: per-parameter structured detail.'
    YoastHead:
      type: object
      description: Yoast SEO head payload for a URL.
      properties:
        json:
          type: object
          description: 'Structured head metadata: title, description, canonical, robots directives, og_* and twitter_*
            properties, and `schema` carrying the schema.org @graph.'
        html:
          type: string
          description: The same metadata as rendered <head> markup.