How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Ascend Elements Yoast/v1 API

The yoast/v1 API from Ascend Elements — 46 operation(s) for yoast/v1.

Ascend Elements Yoast/v1 API is one of 21 APIs that Ascend Elements publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include yoast/v1. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 48 operations across 46 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version wp/v2.

Requests are made against a single base URL, https://ascendelements.com/wp-json.

48 operations 46 paths 1 schemas 1 DELETE17 GET30 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
wp/v2
Base URL
https://ascendelements.com/wp-json
Authentication
HTTP Basic, API Key
Resource Areas
1

Authentication & Security 2

Ascend Elements Yoast/v1 API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (applicationPassword). An API key is passed in the header as X-WP-Nonce (cookieNonce). By default, every request must be authenticated, though some operations may also be called without credentials.

  • applicationPassword — WordPress Application Passwords, advertised by the live route index at https://ascendelements.com/wp-json/ under authentication.application-passwords. Username…
  • cookieNonce — WordPress cookie authentication paired with a nonce on the X-WP-Nonce header, for same-origin first-party callers. Advertised via the access-control-allow-head…

Paths & Operations 48

Across 46 paths, the API surfaces 48 operations — 1 DELETE, 17 GET, 30 POST. Each is listed below with its method, path, parameters, and response codes.

yoast/v1 48
GET
/yoast/v1
GET /yoast/v1
getYoastV1 2 params → 200401404default
POST
/yoast/v1/action_tracking
POST /yoast/v1/actiontracking
createYoastV1ActionTracking body → 200401404default
POST
/yoast/v1/alerts/dismiss
POST /yoast/v1/alerts/dismiss
createYoastV1AlertsDismiss body → 200401404default
GET
/yoast/v1/available_posts
GET /yoast/v1/availableposts
getYoastV1AvailablePosts 2 params → 200401404default
POST
/yoast/v1/complete_task
POST /yoast/v1/completetask
createYoastV1CompleteTask body → 200401404default
GET
/yoast/v1/configuration/check_capability
GET /yoast/v1/configuration/checkcapability
getYoastV1ConfigurationCheckCapability 1 param → 200401404default
POST
/yoast/v1/configuration/enable_tracking
POST /yoast/v1/configuration/enabletracking
createYoastV1ConfigurationEnableTracking body → 200401404default
GET
/yoast/v1/configuration/get_configuration_state
GET /yoast/v1/configuration/getconfigurationstate
getYoastV1ConfigurationGetConfigurationState → 200401404default
POST
/yoast/v1/configuration/save_configuration_state
POST /yoast/v1/configuration/saveconfigurationstate
createYoastV1ConfigurationSaveConfigurationState body → 200401404default
POST
/yoast/v1/configuration/site_representation
POST /yoast/v1/configuration/siterepresentation
createYoastV1ConfigurationSiteRepresentation body → 200401404default
POST
/yoast/v1/configuration/social_profiles
POST /yoast/v1/configuration/socialprofiles
createYoastV1ConfigurationSocialProfiles body → 200401404default
GET
/yoast/v1/file_size
GET /yoast/v1/filesize
getYoastV1FileSize 1 param → 200401404default
GET
/yoast/v1/get_head
GET /yoast/v1/gethead
getYoastV1GetHead 1 param → 200401404default
GET
/yoast/v1/get_tasks
GET /yoast/v1/gettasks
getYoastV1GetTasks 1 param → 200401404default
POST
/yoast/v1/import/{plugin}/{type}
POST /yoast/v1/import/{plugin}/{type}
createYoastV1ImportPluginType 2 params → 200401404default
POST
/yoast/v1/indexing/complete
POST /yoast/v1/indexing/complete
createYoastV1IndexingComplete → 200401404default
POST
/yoast/v1/indexing/general
POST /yoast/v1/indexing/general
createYoastV1IndexingGeneral → 200401404default
POST
/yoast/v1/indexing/indexables-complete
POST /yoast/v1/indexing/indexables-complete
createYoastV1IndexingIndexablesComplete → 200401404default
POST
/yoast/v1/indexing/post-type-archives
POST /yoast/v1/indexing/post-type-archives
createYoastV1IndexingPostTypeArchives → 200401404default
POST
/yoast/v1/indexing/posts
POST /yoast/v1/indexing/posts
createYoastV1IndexingPosts → 200401404default
POST
/yoast/v1/indexing/prepare
POST /yoast/v1/indexing/prepare
createYoastV1IndexingPrepare → 200401404default
POST
/yoast/v1/indexing/terms
POST /yoast/v1/indexing/terms
createYoastV1IndexingTerms → 200401404default
POST
/yoast/v1/integrations/set_active
POST /yoast/v1/integrations/setactive
createYoastV1IntegrationsSetActive body → 200401404default
POST
/yoast/v1/introductions/{introduction_id}/seen
POST /yoast/v1/introductions/{introductionid}/seen
createYoastV1IntroductionsIntroductionIdSeen 1 param body → 200401404default
POST
/yoast/v1/link-indexing/posts
POST /yoast/v1/link-indexing/posts
createYoastV1LinkIndexingPosts → 200401404default
POST
/yoast/v1/link-indexing/terms
POST /yoast/v1/link-indexing/terms
createYoastV1LinkIndexingTerms → 200401404default
GET
/yoast/v1/meta/search
GET /yoast/v1/meta/search
getYoastV1MetaSearch → 200401404default
POST
/yoast/v1/new-content-type-visibility/dismiss-post-type
POST /yoast/v1/new-content-type-visibility/dismiss-post-type
createYoastV1NewContentTypeVisibilityDismissPostType body → 200401404default
POST
/yoast/v1/new-content-type-visibility/dismiss-taxonomy
POST /yoast/v1/new-content-type-visibility/dismiss-taxonomy
createYoastV1NewContentTypeVisibilityDismissTaxonomy body → 200401404default
GET
/yoast/v1/readability_scores
GET /yoast/v1/readabilityscores
getYoastV1ReadabilityScores 4 params → 200401404default
POST
/yoast/v1/semrush/authenticate
POST /yoast/v1/semrush/authenticate
createYoastV1SemrushAuthenticate body → 200401404default
POST
/yoast/v1/semrush/country_code
POST /yoast/v1/semrush/countrycode
createYoastV1SemrushCountryCode body → 200401404default
GET
/yoast/v1/semrush/related_keyphrases
GET /yoast/v1/semrush/relatedkeyphrases
getYoastV1SemrushRelatedKeyphrases 2 params → 200401404default
GET
/yoast/v1/seo_scores
GET /yoast/v1/seoscores
getYoastV1SeoScores 4 params → 200401404default
POST
/yoast/v1/setup_steps_tracking
POST /yoast/v1/setupstepstracking
createYoastV1SetupStepsTracking body → 200401404default
POST
/yoast/v1/site_kit_configuration_permanent_dismissal
POST /yoast/v1/sitekitconfigurationpermanentdismissal
createYoastV1SiteKitConfigurationPermanentDismissal body → 200401404default
GET
/yoast/v1/statistics
GET /yoast/v1/statistics
getYoastV1Statistics → 200401404default
GET
/yoast/v1/wincher/account/limit
GET /yoast/v1/wincher/account/limit
getYoastV1WincherAccountLimit → 200401404default
GET
/yoast/v1/wincher/account/upgrade-campaign
GET /yoast/v1/wincher/account/upgrade-campaign
getYoastV1WincherAccountUpgradeCampaign → 200401404default
POST
/yoast/v1/wincher/authenticate
POST /yoast/v1/wincher/authenticate
createYoastV1WincherAuthenticate body → 200401404default
GET
/yoast/v1/wincher/authorization-url
GET /yoast/v1/wincher/authorization-url
getYoastV1WincherAuthorizationUrl → 200401404default
POST
/yoast/v1/wincher/keyphrases
POST /yoast/v1/wincher/keyphrases
createYoastV1WincherKeyphrases body → 200401404default
POST
/yoast/v1/wincher/keyphrases/track
POST /yoast/v1/wincher/keyphrases/track
createYoastV1WincherKeyphrasesTrack body → 200401404default
DELETE
/yoast/v1/wincher/keyphrases/untrack
DELETE /yoast/v1/wincher/keyphrases/untrack
deleteYoastV1WincherKeyphrasesUntrack → 200401404default
GET
/yoast/v1/wistia_embed_permission
GET /yoast/v1/wistiaembedpermission
getYoastV1WistiaEmbedPermission → 200401404default
POST
/yoast/v1/wistia_embed_permission
POST /yoast/v1/wistiaembedpermission
createYoastV1WistiaEmbedPermission body → 200401404default
GET
/yoast/v1/workouts
GET /yoast/v1/workouts
getYoastV1Workouts → 200401404default
POST
/yoast/v1/workouts
POST /yoast/v1/workouts
createYoastV1Workouts → 200401404default

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is RestError (3 properties). Each schema is shown below with its type and property counts.

RestError
object
The WordPress REST API error envelope, observed live on this host (GET /wp-json/wp-abilities/v1/abilities returns restforbidden with status 401; GET /wp-json/w…
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ascend-elements-yoast-v1-api-openapi.yml Raw ↑

Other APIs Ascend Elements publishes across the network.

Ascend Elements Complianz/v1 API
Ascend Elements Core API
Ascend Elements Cptui/v1 API
Ascend Elements Ea11y/v1 API
Ascend Elements Elementor Ai/v1 API
Ascend Elements Elementor One/v1 API
Ascend Elements Elementor Pro/v1 API
Ascend Elements Elementor/v1 API
Ascend Elements Elementor/v1/documents API
Ascend Elements Elementor/v1/feedback API
Ascend Elements Facetwp/v1 API
Ascend Elements Image Optimizer/v1 API
Where this information came from

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