generated: '2026-07-19'
method: derived
source: openapi/leapcure-blog-content-openapi.yml (derived from https://blog.leapcure.com/wp-json/wp/v2)
scope: >-
  Cross-cutting request/response semantics for the one machine-readable API surface Leapcure
  operates: the WordPress REST API behind blog.leapcure.com. Leapcure's clinical-trial recruitment
  business itself publishes no developer API, so these conventions describe the blog content API
  only. Everything below was observed in the live route metadata or the live responses; nothing is
  assumed from generic WordPress documentation that was not confirmed on this host.
authentication:
  style: http-basic
  scheme: WordPress application passwords
  authorization_url: https://blog.leapcure.com/wp-admin/authorize-application.php
  anonymous_read: true
  anonymous_read_verified:
  - posts
  - pages
  - categories
  - tags
  - users
  - media
  - comments
  - search
  - taxonomies
  - types
  - statuses
  authenticated_only_verified:
  - settings
  writes_require_auth: true
  detail: authentication/leapcure-authentication.yml
idempotency:
  supported: false
  note: >-
    No idempotency key header or parameter is exposed by any route in the published route metadata.
    No Idempotency pointer is emitted for this provider.
pagination:
  style: page-number
  parameters:
  - name: page
    in: query
    default: 1
    description: Current page of the collection.
  - name: per_page
    in: query
    default: 10
    description: Maximum number of items to be returned in result set.
  - name: offset
    in: query
    description: Offset the result set by a specific number of items (collection routes).
  response_headers:
  - name: X-WP-Total
    description: Total number of items in the collection.
  - name: X-WP-TotalPages
    description: Total number of pages available at the current per_page size.
  link_header: true
  link_header_note: RFC 8288 Link header carries rel="next" / rel="prev" on collection responses.
ordering:
  parameters:
  - name: order
    values: [asc, desc]
  - name: orderby
    description: Per-resource sort attribute; allowed values are enumerated per route in the OpenAPI.
filtering:
  parameters:
  - name: search
    description: Limit results to those matching a string.
  - name: include
    description: Limit result set to specific IDs.
  - name: exclude
    description: Ensure result set excludes specific IDs.
  - name: slug
    description: Limit result set to items with one or more specific slugs.
  - name: after
    description: Limit response to items published after a given ISO 8601 date-time.
  - name: before
    description: Limit response to items published before a given ISO 8601 date-time.
field_selection:
  style: context-and-fields
  parameters:
  - name: context
    values: [view, embed, edit]
    default: view
    description: Scope under which the request is made; determines which fields are present in the response.
  - name: _fields
    description: Sparse fieldset selection (WordPress core query parameter).
  - name: _embed
    description: Inline embedded resources (author, terms, featured media) via the _embedded envelope.
hypermedia:
  style: HAL-like
  note: Responses carry a `_links` object and, when `_embed` is requested, an `_embedded` object.
versioning:
  scheme: namespace-in-path
  current: wp/v2
  base: https://blog.leapcure.com/wp-json
  discovery: https://blog.leapcure.com/wp-json/
  namespaces_advertised: 37
  detail: lifecycle/leapcure-lifecycle.yml
error_envelope:
  media_type: application/json
  format: wordpress-rest-error
  rfc9457: false
  shape:
    code: Machine-readable error code, e.g. rest_forbidden.
    message: Human-readable error message.
    data.status: Repeated HTTP status code.
  observed_example:
    code: rest_forbidden
    message: Sorry, you are not allowed to do that.
    data:
      status: 401
  detail: errors/leapcure-problem-types.yml
rate_limits:
  published: false
  note: >-
    No rate-limit policy is published for this host and no RateLimit/X-RateLimit headers were
    observed on probed responses. Not asserted either way.
request_tracing:
  request_id_header: null
  note: No provider-specific request-id header was observed.
content_negotiation:
  request: application/json
  response: application/json
  method_override_header: X-HTTP-Method-Override
  method_override_note: >-
    WordPress accepts POST with X-HTTP-Method-Override for PUT/PATCH/DELETE where clients cannot
    issue those verbs.
related:
- authentication/leapcure-authentication.yml
- errors/leapcure-problem-types.yml
- lifecycle/leapcure-lifecycle.yml
- data-model/leapcure-data-model.yml