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 Elementor One/v1 API

The elementor-one/v1 API from Ascend Elements — 16 operation(s) for elementor-one/v1.

Ascend Elements Elementor One/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 elementor-one/v1. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 20 operations across 16 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.

20 operations 16 paths 1 schemas 4 GET1 PATCH14 POST1 PUT

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 Elementor One/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 20

Across 16 paths, the API surfaces 20 operations — 4 GET, 1 PATCH, 14 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

elementor-one/v1 20
GET
/elementor-one/v1
GET /elementor-one/v1
getElementorOneV1 2 params → 200401404default
POST
/elementor-one/v1/connect/authorize
POST /elementor-one/v1/connect/authorize
createElementorOneV1ConnectAuthorize body → 200401404default
POST
/elementor-one/v1/connect/deactivate
POST /elementor-one/v1/connect/deactivate
createElementorOneV1ConnectDeactivate → 200401404default
POST
/elementor-one/v1/connect/disconnect
POST /elementor-one/v1/connect/disconnect
createElementorOneV1ConnectDisconnect → 200401404default
POST
/elementor-one/v1/connect/switch-domain
POST /elementor-one/v1/connect/switch-domain
createElementorOneV1ConnectSwitchDomain → 200401404default
GET
/elementor-one/v1/plugins
GET /elementor-one/v1/plugins
getElementorOneV1Plugins 3 params → 200401404default
POST
/elementor-one/v1/plugins
POST /elementor-one/v1/plugins
createElementorOneV1Plugins body → 200401404default
POST
/elementor-one/v1/plugins/{slug}/activate
POST /elementor-one/v1/plugins/{slug}/activate
createElementorOneV1PluginsSlugActivate 1 param → 200401404default
POST
/elementor-one/v1/plugins/{slug}/deactivate
POST /elementor-one/v1/plugins/{slug}/deactivate
createElementorOneV1PluginsSlugDeactivate 1 param → 200401404default
POST
/elementor-one/v1/plugins/{slug}/migration/rollback
POST /elementor-one/v1/plugins/{slug}/migration/rollback
createElementorOneV1PluginsSlugMigrationRollback 1 param → 200401404default
POST
/elementor-one/v1/plugins/{slug}/migration/run
POST /elementor-one/v1/plugins/{slug}/migration/run
createElementorOneV1PluginsSlugMigrationRun 1 param body → 200401404default
POST
/elementor-one/v1/plugins/{slug}/upgrade
POST /elementor-one/v1/plugins/{slug}/upgrade
createElementorOneV1PluginsSlugUpgrade 1 param body → 200401404default
GET
/elementor-one/v1/settings
GET /elementor-one/v1/settings
getElementorOneV1Settings → 200401404default
POST
/elementor-one/v1/settings
POST /elementor-one/v1/settings
createElementorOneV1Settings → 200401404default
PUT
/elementor-one/v1/settings
PUT /elementor-one/v1/settings
updateElementorOneV1Settings → 200401404default
PATCH
/elementor-one/v1/settings
PATCH /elementor-one/v1/settings
patchElementorOneV1Settings → 200401404default
POST
/elementor-one/v1/themes
POST /elementor-one/v1/themes
createElementorOneV1Themes body → 200401404default
POST
/elementor-one/v1/themes/{slug}/activate
POST /elementor-one/v1/themes/{slug}/activate
createElementorOneV1ThemesSlugActivate 1 param → 200401404default
POST
/elementor-one/v1/top-bar/feedback
POST /elementor-one/v1/top-bar/feedback
createElementorOneV1TopBarFeedback body → 200401404default
GET
/elementor-one/v1/top-bar/notifications
GET /elementor-one/v1/top-bar/notifications
getElementorOneV1TopBarNotifications 2 params → 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-elementor-one-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 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
Ascend Elements Oembed/1.0 API
Where this information came from

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