Ascend Elements Site Mailer/v1 API
The site-mailer/v1 API from Ascend Elements — 21 operation(s) for site-mailer/v1.
The site-mailer/v1 API from Ascend Elements — 21 operation(s) for site-mailer/v1.
openapi: 3.2.0
info:
title: Ascend Elements WordPress REST Site Mailer/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: site-mailer/v1
paths:
/site-mailer/v1:
get:
operationId: getSiteMailerV1
summary: GET /site-mailer/v1
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1` in the `site-mailer/v1` namespace.
tags:
- site-mailer/v1
parameters:
- name: namespace
in: query
schema:
default: site-mailer/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'
/site-mailer/v1/connect/authorize:
post:
operationId: createSiteMailerV1ConnectAuthorize
summary: POST /site-mailer/v1/connect/authorize
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/connect/authorize` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/connect/deactivate:
post:
operationId: createSiteMailerV1ConnectDeactivate
summary: POST /site-mailer/v1/connect/deactivate
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/connect/deactivate` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/connect/disconnect:
post:
operationId: createSiteMailerV1ConnectDisconnect
summary: POST /site-mailer/v1/connect/disconnect
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/connect/disconnect` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/connect/switch-domain:
post:
operationId: createSiteMailerV1ConnectSwitchDomain
summary: POST /site-mailer/v1/connect/switch-domain
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/connect/switch-domain` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/domain/delete:
post:
operationId: createSiteMailerV1DomainDelete
summary: POST /site-mailer/v1/domain/delete
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/domain/delete` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/domain/register:
post:
operationId: createSiteMailerV1DomainRegister
summary: POST /site-mailer/v1/domain/register
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/domain/register` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/domain/verify:
post:
operationId: createSiteMailerV1DomainVerify
summary: POST /site-mailer/v1/domain/verify
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/domain/verify` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/logs/delete-logs:
delete:
operationId: deleteSiteMailerV1LogsDeleteLogs
summary: DELETE /site-mailer/v1/logs/delete-logs
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/logs/delete-logs` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/logs/get-logs:
get:
operationId: getSiteMailerV1LogsGetLogs
summary: GET /site-mailer/v1/logs/get-logs
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/logs/get-logs` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/logs/refresh-statuses:
get:
operationId: getSiteMailerV1LogsRefreshStatuses
summary: GET /site-mailer/v1/logs/refresh-statuses
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/logs/refresh-statuses` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/mailer/resend-mails:
post:
operationId: createSiteMailerV1MailerResendMails
summary: POST /site-mailer/v1/mailer/resend-mails
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/mailer/resend-mails` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/mailer/send-test-mail:
post:
operationId: createSiteMailerV1MailerSendTestMail
summary: POST /site-mailer/v1/mailer/send-test-mail
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/mailer/send-test-mail` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/reviews/review:
post:
operationId: createSiteMailerV1ReviewsReview
summary: POST /site-mailer/v1/reviews/review
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/reviews/review` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/settings/get-settings:
get:
operationId: getSiteMailerV1SettingsGetSettings
summary: GET /site-mailer/v1/settings/get-settings
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/settings/get-settings` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/statuses/get-stats:
get:
operationId: getSiteMailerV1StatusesGetStats
summary: GET /site-mailer/v1/statuses/get-stats
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/statuses/get-stats` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/statuses/get-statuses:
get:
operationId: getSiteMailerV1StatusesGetStatuses
summary: GET /site-mailer/v1/statuses/get-statuses
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/statuses/get-statuses` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/suppressions/add-suppression:
post:
operationId: createSiteMailerV1SuppressionsAddSuppression
summary: POST /site-mailer/v1/suppressions/add-suppression
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/suppressions/add-suppression` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/suppressions/delete-suppressions:
delete:
operationId: deleteSiteMailerV1SuppressionsDeleteSuppressions
summary: DELETE /site-mailer/v1/suppressions/delete-suppressions
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/suppressions/delete-suppressions` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/suppressions/get-suppressions:
get:
operationId: getSiteMailerV1SuppressionsGetSuppressions
summary: GET /site-mailer/v1/suppressions/get-suppressions
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/suppressions/get-suppressions` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
/site-mailer/v1/suppressions/unsubscribe/{email}:
parameters:
- name: email
in: path
required: true
description: Path segment `email` from the WordPress route pattern `/site-mailer/v1/suppressions/unsubscribe/(?P<email>[a-zA-Z0-9=_-]+)`.
schema:
type: string
get:
operationId: getSiteMailerV1SuppressionsUnsubscribeEmail
summary: GET /site-mailer/v1/suppressions/unsubscribe/{email}
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/suppressions/unsubscribe/(?P<email>[a-zA-Z0-9=_-]+)` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
post:
operationId: createSiteMailerV1SuppressionsUnsubscribeEmail
summary: POST /site-mailer/v1/suppressions/unsubscribe/{email}
description: Operation advertised by the WordPress REST route index at https://ascendelements.com/wp-json/ for route `/site-mailer/v1/suppressions/unsubscribe/(?P<email>[a-zA-Z0-9=_-]+)` in the `site-mailer/v1` namespace.
tags:
- site-mailer/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'
components:
schemas:
RestError:
type: object
description: The WordPress REST API error envelope, observed live on this host (GET /wp-json/wp-abilities/v1/abilities returns rest_forbidden with status 401; GET /wp-json/wp/v2/menus returns rest_cannot_view with status 401).
properties:
code:
type: string
description: Machine-readable error code, e.g. rest_forbidden, rest_cannot_view, rest_no_route.
message:
type: string
description: Human-readable error message.
data:
type: object
properties:
status:
type: integer
description: HTTP status code.
required:
- code
- message
securitySchemes:
applicationPassword:
type: http
scheme: basic
description: WordPress Application Passwords, advertised by the live route index at https://ascendelements.com/wp-json/ under authentication.application-passwords. Username + application password presented as HTTP Basic on the Authorization header. Issued at https://ascendelements.com/wp-admin/authorize-application.php.
cookieNonce:
type: apiKey
in: header
name: X-WP-Nonce
description: 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-headers response header observed live on this host.