Ascend Elements WordPress REST API

The WordPress REST API surface published by Ascend Elements at ascendelements.com/wp-json — 362 routes across 20 namespaces. The anonymously readable core is the wp/v2 content surface (posts, pages, media, categories, tags, users, comments, search, types, taxonomies, statuses) plus three company-specific custom post types: media_coverage (61 items of press coverage), sourcing-events (open supplier bid packages for the Apex 1 plant) and job (the careers board, currently empty) with its job_category and job_location taxonomies. This is the corporate website's content/CMS surface, not a product API for Ascend Elements' battery materials, recycling or logistics business — the company ships no public developer API for those. The OpenAPI in this repo was derived mechanically from the live route index and from JSON Schemas returned by HTTP OPTIONS on the readable collections.

OpenAPI Specification

ascend-elements-wordpress-rest-openapi.yml Raw ↑
openapi: 3.1.0
info:
  title: Ascend Elements WordPress REST API
  version: wp/v2
  summary: The machine-readable REST surface published at ascendelements.com/wp-json.
  description: 'The WordPress REST API surface published by Ascend Elements at https://ascendelements.com/wp-json/. This document
    was DERIVED mechanically from the live route index -- every path, method and parameter below appears in that index --
    and component schemas were harvested from live HTTP OPTIONS responses on the anonymously readable wp/v2 collections. Alongside
    the WordPress core content collections it covers three company-specific custom post types: `media_coverage` (press coverage),
    `sourcing-events` (open supplier bid packages for the Apex 1 plant) and `job` (careers board), with the `job_category`
    and `job_location` taxonomies. It is NOT a product API for Ascend Elements'' battery materials, recycling or logistics
    business -- the company publishes no public developer API for those. Most non-wp/v2 namespaces (Elementor, Yoast, Site
    Mailer, Image Optimizer, WP Engine, Complianz admin routes) and the WordPress Abilities API require an authenticated administrative
    session and return rest_forbidden / 401 anonymously.'
  contact:
    email: info@ascendelements.com
    url: https://ascendelements.com/
  x-derived-from: https://ascendelements.com/wp-json/
  x-derived-on: '2026-08-02'
  x-derived-by: API Evangelist enrichment pipeline (local-v1)
servers:
- url: https://ascendelements.com/wp-json
  description: Ascend Elements WordPress REST API
tags:
- name: complianz/v1
- name: core
- name: cptui/v1
- name: ea11y/v1
- name: elementor-ai/v1
- name: elementor-one/v1
- name: elementor-pro/v1
- name: elementor/v1
- name: elementor/v1/documents
- name: elementor/v1/feedback
- name: facetwp/v1
- name: image-optimizer/v1
- name: oembed/1.0
- name: site-mailer/v1
- name: wp-abilities/v1
- name: wp-block-editor/v1
- name: wp-site-health/v1
- name: wp/v2
- name: wpe/cache-plugin/v1
- name: wpe_sign_on_plugin/v1
- name: yoast/v1
paths:
  /:
    get:
      operationId: getRoot
      summary: GET /
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/` in the `core` namespace.
      tags:
      - core
      parameters:
      - name: context
        in: query
        schema:
          default: view
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /batch/v1:
    post:
      operationId: createBatchV1
      summary: POST /batch/v1
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/batch/v1` in the `core` namespace.
      tags:
      - core
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                validation:
                  type: string
                  enum:
                  - require-all-validate
                  - normal
                  default: normal
                requests:
                  type: array
                  items:
                    type: object
              required:
              - requests
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /complianz/v1:
    get:
      operationId: getComplianzV1
      summary: GET /complianz/v1
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/complianz/v1` in the `complianz/v1` namespace.
      tags:
      - complianz/v1
      parameters:
      - name: namespace
        in: query
        schema:
          default: complianz/v1
      - name: context
        in: query
        schema:
          default: view
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /complianz/v1/banner:
    get:
      operationId: getComplianzV1Banner
      summary: GET /complianz/v1/banner
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/complianz/v1/banner` in the `complianz/v1` namespace.
      tags:
      - complianz/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /complianz/v1/consent-area/{post_id}/{block_id}:
    parameters:
    - name: post_id
      in: path
      required: true
      description: Path segment `post_id` from the WordPress route pattern `/complianz/v1/consent-area/(?P<post_id>([0-9]+))/(?P<block_id>([a-z0-9-_]+))`.
      schema:
        type: string
    - name: block_id
      in: path
      required: true
      description: Path segment `block_id` from the WordPress route pattern `/complianz/v1/consent-area/(?P<post_id>([0-9]+))/(?P<block_id>([a-z0-9-_]+))`.
      schema:
        type: string
    get:
      operationId: getComplianzV1ConsentAreaPostIdBlockId
      summary: GET /complianz/v1/consent-area/{post_id}/{block_id}
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/complianz/v1/consent-area/(?P<post_id>([0-9]+))/(?P<block_id>([a-z0-9-_]+))` in the `complianz/v1` namespace.
      tags:
      - complianz/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /complianz/v1/cookie_data:
    get:
      operationId: getComplianzV1CookieData
      summary: GET /complianz/v1/cookie_data
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/complianz/v1/cookie_data` in the `complianz/v1` namespace.
      tags:
      - complianz/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /complianz/v1/datarequests:
    post:
      operationId: createComplianzV1Datarequests
      summary: POST /complianz/v1/datarequests
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/complianz/v1/datarequests` in the `complianz/v1` namespace.
      tags:
      - complianz/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /complianz/v1/documents:
    get:
      operationId: getComplianzV1Documents
      summary: GET /complianz/v1/documents
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/complianz/v1/documents` in the `complianz/v1` namespace.
      tags:
      - complianz/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /complianz/v1/manage_consent_html:
    get:
      operationId: getComplianzV1ManageConsentHtml
      summary: GET /complianz/v1/manage_consent_html
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/complianz/v1/manage_consent_html` in the `complianz/v1` namespace.
      tags:
      - complianz/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /complianz/v1/store_cookies:
    post:
      operationId: createComplianzV1StoreCookies
      summary: POST /complianz/v1/store_cookies
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/complianz/v1/store_cookies` in the `complianz/v1` namespace.
      tags:
      - complianz/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /complianz/v1/track:
    post:
      operationId: createComplianzV1Track
      summary: POST /complianz/v1/track
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/complianz/v1/track` in the `complianz/v1` namespace.
      tags:
      - complianz/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /complianz/v1/wsc-checks:
    post:
      operationId: createComplianzV1WscChecks
      summary: POST /complianz/v1/wsc-checks
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/complianz/v1/wsc-checks` in the `complianz/v1` namespace.
      tags:
      - complianz/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /complianz/v1/wsc-scan:
    post:
      operationId: createComplianzV1WscScan
      summary: POST /complianz/v1/wsc-scan
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/complianz/v1/wsc-scan` in the `complianz/v1` namespace.
      tags:
      - complianz/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /cptui/v1:
    get:
      operationId: getCptuiV1
      summary: GET /cptui/v1
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/cptui/v1` in the `cptui/v1` namespace.
      tags:
      - cptui/v1
      parameters:
      - name: namespace
        in: query
        schema:
          default: cptui/v1
      - name: context
        in: query
        schema:
          default: view
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /cptui/v1/dismiss-pro-upsell:
    post:
      operationId: createCptuiV1DismissProUpsell
      summary: POST /cptui/v1/dismiss-pro-upsell
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/cptui/v1/dismiss-pro-upsell` in the `cptui/v1` namespace.
      tags:
      - cptui/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /ea11y/v1:
    get:
      operationId: getEa11yV1
      summary: GET /ea11y/v1
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/ea11y/v1` in the `ea11y/v1` namespace.
      tags:
      - ea11y/v1
      parameters:
      - name: namespace
        in: query
        schema:
          default: ea11y/v1
      - name: context
        in: query
        schema:
          default: view
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /ea11y/v1/analytics/statistic:
    get:
      operationId: getEa11yV1AnalyticsStatistic
      summary: GET /ea11y/v1/analytics/statistic
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/ea11y/v1/analytics/statistic` in the `ea11y/v1` namespace.
      tags:
      - ea11y/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /ea11y/v1/connect/authorize:
    post:
      operationId: createEa11yV1ConnectAuthorize
      summary: POST /ea11y/v1/connect/authorize
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/ea11y/v1/connect/authorize` in the `ea11y/v1` namespace.
      tags:
      - ea11y/v1
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                clearSession:
                  type: boolean
                  default: false
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /ea11y/v1/connect/deactivate:
    post:
      operationId: createEa11yV1ConnectDeactivate
      summary: POST /ea11y/v1/connect/deactivate
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/ea11y/v1/connect/deactivate` in the `ea11y/v1` namespace.
      tags:
      - ea11y/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /ea11y/v1/connect/disconnect:
    post:
      operationId: createEa11yV1ConnectDisconnect
      summary: POST /ea11y/v1/connect/disconnect
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/ea11y/v1/connect/disconnect` in the `ea11y/v1` namespace.
      tags:
      - ea11y/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /ea11y/v1/connect/switch-domain:
    post:
      operationId: createEa11yV1ConnectSwitchDomain
      summary: POST /ea11y/v1/connect/switch-domain
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/ea11y/v1/connect/switch-domain` in the `ea11y/v1` namespace.
      tags:
      - ea11y/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /ea11y/v1/remediation/clear-cache:
    delete:
      operationId: deleteEa11yV1RemediationClearCache
      summary: DELETE /ea11y/v1/remediation/clear-cache
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/ea11y/v1/remediation/clear-cache` in the `ea11y/v1` namespace.
      tags:
      - ea11y/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /ea11y/v1/remediation/dismiss-heading-issue:
    post:
      operationId: createEa11yV1RemediationDismissHeadingIssue
      summary: POST /ea11y/v1/remediation/dismiss-heading-issue
      description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route
        `/ea11y/v1/remediation/dismiss-heading-issue` in the `ea11y/v1` namespace.
      tags:
      - ea11y/v1
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Authentication required or insufficient capability (rest_forbidden / rest_cannot_view). Observed live
            on wp-abilities/v1 and wp/v2/menus.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        '404':
          description: No route or resource matched (rest_no_route).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
        default:
          description: WordPress REST error envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RestError'
  /ea11y/v1/remediation/global-item:
    post:
      operationId: createEa11yV1RemediationGlobalItem
      summary: POST /ea11y/v1/remediation/global-item
      desc

# --- truncated at 32 KB (1303 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/ascend-elements/refs/heads/main/openapi/ascend-elements-wordpress-rest-openapi.yml
Where this information came from

This is an independent, third-party profile of Ascend Elements WordPress REST 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.