Ascend Elements Yoast/v1 API
The yoast/v1 API from Ascend Elements — 46 operation(s) for yoast/v1.
The yoast/v1 API from Ascend Elements — 46 operation(s) for yoast/v1.
openapi: 3.2.0
info:
title: Ascend Elements WordPress REST Yoast/v1 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
security:
- {}
- applicationPassword: []
- cookieNonce: []
tags:
- name: yoast/v1
paths:
/yoast/v1:
get:
operationId: getYoastV1
summary: GET /yoast/v1
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1` in the `yoast/v1` namespace.
tags:
- yoast/v1
parameters:
- name: namespace
in: query
schema:
default: yoast/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'
/yoast/v1/action_tracking:
post:
operationId: createYoastV1ActionTracking
summary: POST /yoast/v1/action_tracking
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/action_tracking` in the `yoast/v1` namespace.
tags:
- yoast/v1
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
action:
type: string
required:
- action
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'
/yoast/v1/alerts/dismiss:
post:
operationId: createYoastV1AlertsDismiss
summary: POST /yoast/v1/alerts/dismiss
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/alerts/dismiss` in the `yoast/v1` namespace.
tags:
- yoast/v1
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
key:
type: string
required:
- key
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'
/yoast/v1/available_posts:
get:
operationId: getYoastV1AvailablePosts
summary: GET /yoast/v1/available_posts
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/available_posts` in the `yoast/v1` namespace.
tags:
- yoast/v1
parameters:
- name: search
in: query
schema:
type: string
default: ''
- name: postType
in: query
schema:
type: string
default: page
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'
/yoast/v1/complete_task:
post:
operationId: createYoastV1CompleteTask
summary: POST /yoast/v1/complete_task
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/complete_task` in the `yoast/v1` namespace.
tags:
- yoast/v1
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
options:
type: object
properties:
task:
type: string
required:
- options
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'
/yoast/v1/configuration/check_capability:
get:
operationId: getYoastV1ConfigurationCheckCapability
summary: GET /yoast/v1/configuration/check_capability
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/configuration/check_capability` in the `yoast/v1` namespace.
tags:
- yoast/v1
parameters:
- name: user_id
in: query
schema:
type: string
required: true
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'
/yoast/v1/configuration/enable_tracking:
post:
operationId: createYoastV1ConfigurationEnableTracking
summary: POST /yoast/v1/configuration/enable_tracking
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/configuration/enable_tracking` in the `yoast/v1` namespace.
tags:
- yoast/v1
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
tracking:
type: boolean
required:
- tracking
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'
/yoast/v1/configuration/get_configuration_state:
get:
operationId: getYoastV1ConfigurationGetConfigurationState
summary: GET /yoast/v1/configuration/get_configuration_state
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/configuration/get_configuration_state` in the `yoast/v1` namespace.
tags:
- yoast/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'
/yoast/v1/configuration/save_configuration_state:
post:
operationId: createYoastV1ConfigurationSaveConfigurationState
summary: POST /yoast/v1/configuration/save_configuration_state
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/configuration/save_configuration_state` in the `yoast/v1` namespace.
tags:
- yoast/v1
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
finishedSteps:
type: array
required:
- finishedSteps
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'
/yoast/v1/configuration/site_representation:
post:
operationId: createYoastV1ConfigurationSiteRepresentation
summary: POST /yoast/v1/configuration/site_representation
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/configuration/site_representation` in the `yoast/v1` namespace.
tags:
- yoast/v1
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
company_or_person:
type: string
enum:
- company
- person
company_name:
type: string
company_logo:
type: string
company_logo_id:
type: integer
person_logo:
type: string
person_logo_id:
type: integer
company_or_person_user_id:
type: integer
description:
type: string
required:
- company_or_person
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'
/yoast/v1/configuration/social_profiles:
post:
operationId: createYoastV1ConfigurationSocialProfiles
summary: POST /yoast/v1/configuration/social_profiles
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/configuration/social_profiles` in the `yoast/v1` namespace.
tags:
- yoast/v1
requestBody:
required: false
content:
application/json:
schema:
type: object
properties:
facebook_site:
type: string
twitter_site:
type: string
other_social_urls:
type: array
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'
/yoast/v1/file_size:
get:
operationId: getYoastV1FileSize
summary: GET /yoast/v1/file_size
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/file_size` in the `yoast/v1` namespace.
tags:
- yoast/v1
parameters:
- name: url
in: query
schema:
type: string
description: The url to retrieve
required: true
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'
/yoast/v1/get_head:
get:
operationId: getYoastV1GetHead
summary: GET /yoast/v1/get_head
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/get_head` in the `yoast/v1` namespace.
tags:
- yoast/v1
parameters:
- name: url
in: query
schema:
type: string
required: true
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'
/yoast/v1/get_tasks:
get:
operationId: getYoastV1GetTasks
summary: GET /yoast/v1/get_tasks
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/get_tasks` in the `yoast/v1` namespace.
tags:
- yoast/v1
parameters:
- name: options
in: query
schema:
type: object
properties:
filter:
type: string
limit:
type: int
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'
/yoast/v1/import/{plugin}/{type}:
parameters:
- name: plugin
in: path
required: true
description: Path segment `plugin` from the WordPress route pattern `/yoast/v1/import/(?P<plugin>[\w-]+)/(?P<type>[\w-]+)`.
schema:
type: string
- name: type
in: path
required: true
description: Path segment `type` from the WordPress route pattern `/yoast/v1/import/(?P<plugin>[\w-]+)/(?P<type>[\w-]+)`.
schema:
type: string
post:
operationId: createYoastV1ImportPluginType
summary: POST /yoast/v1/import/{plugin}/{type}
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/import/(?P<plugin>[\w-]+)/(?P<type>[\w-]+)` in the `yoast/v1` namespace.
tags:
- yoast/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'
/yoast/v1/indexing/complete:
post:
operationId: createYoastV1IndexingComplete
summary: POST /yoast/v1/indexing/complete
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/indexing/complete` in the `yoast/v1` namespace.
tags:
- yoast/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'
/yoast/v1/indexing/general:
post:
operationId: createYoastV1IndexingGeneral
summary: POST /yoast/v1/indexing/general
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/indexing/general` in the `yoast/v1` namespace.
tags:
- yoast/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'
/yoast/v1/indexing/indexables-complete:
post:
operationId: createYoastV1IndexingIndexablesComplete
summary: POST /yoast/v1/indexing/indexables-complete
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/indexing/indexables-complete` in the `yoast/v1` namespace.
tags:
- yoast/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'
/yoast/v1/indexing/post-type-archives:
post:
operationId: createYoastV1IndexingPostTypeArchives
summary: POST /yoast/v1/indexing/post-type-archives
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/indexing/post-type-archives` in the `yoast/v1` namespace.
tags:
- yoast/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'
/yoast/v1/indexing/posts:
post:
operationId: createYoastV1IndexingPosts
summary: POST /yoast/v1/indexing/posts
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/indexing/posts` in the `yoast/v1` namespace.
tags:
- yoast/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'
/yoast/v1/indexing/prepare:
post:
operationId: createYoastV1IndexingPrepare
summary: POST /yoast/v1/indexing/prepare
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/indexing/prepare` in the `yoast/v1` namespace.
tags:
- yoast/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'
/yoast/v1/indexing/terms:
post:
operationId: createYoastV1IndexingTerms
summary: POST /yoast/v1/indexing/terms
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/yoast/v1/indexing/terms` in the `yoast/v1` namespace.
tags:
- yoast/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:
$re
# --- truncated at 32 KB (70 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/ascend-elements/refs/heads/main/openapi/ascend-elements-yoast-v1-api-openapi.yml