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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Ascend Elements

Ascend Elements Site Mailer/v1 API

The site-mailer/v1 API from Ascend Elements — 21 operation(s) for site-mailer/v1.

Documentation Provider Profile APIs.io OpenAPI GitHub

Ascend Elements Site Mailer/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 site-mailer/v1. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 22 operations across 21 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.

22 operations 21 paths 1 schemas 2 DELETE8 GET12 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
Contact
https://ascendelements.com/
Resource Areas
1

Authentication & Security 2

Ascend Elements Site Mailer/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 22

Across 21 paths, the API surfaces 22 operations — 2 DELETE, 8 GET, 12 POST. Each is listed below with its method, path, parameters, and response codes.

site-mailer/v1 22
GET
/site-mailer/v1
GET /site-mailer/v1
getSiteMailerV1 2 params → 200401404default
POST
/site-mailer/v1/connect/authorize
POST /site-mailer/v1/connect/authorize
createSiteMailerV1ConnectAuthorize body → 200401404default
POST
/site-mailer/v1/connect/deactivate
POST /site-mailer/v1/connect/deactivate
createSiteMailerV1ConnectDeactivate → 200401404default
POST
/site-mailer/v1/connect/disconnect
POST /site-mailer/v1/connect/disconnect
createSiteMailerV1ConnectDisconnect → 200401404default
POST
/site-mailer/v1/connect/switch-domain
POST /site-mailer/v1/connect/switch-domain
createSiteMailerV1ConnectSwitchDomain → 200401404default
POST
/site-mailer/v1/domain/delete
POST /site-mailer/v1/domain/delete
createSiteMailerV1DomainDelete → 200401404default
POST
/site-mailer/v1/domain/register
POST /site-mailer/v1/domain/register
createSiteMailerV1DomainRegister → 200401404default
POST
/site-mailer/v1/domain/verify
POST /site-mailer/v1/domain/verify
createSiteMailerV1DomainVerify → 200401404default
DELETE
/site-mailer/v1/logs/delete-logs
DELETE /site-mailer/v1/logs/delete-logs
deleteSiteMailerV1LogsDeleteLogs → 200401404default
GET
/site-mailer/v1/logs/get-logs
GET /site-mailer/v1/logs/get-logs
getSiteMailerV1LogsGetLogs → 200401404default
GET
/site-mailer/v1/logs/refresh-statuses
GET /site-mailer/v1/logs/refresh-statuses
getSiteMailerV1LogsRefreshStatuses → 200401404default
POST
/site-mailer/v1/mailer/resend-mails
POST /site-mailer/v1/mailer/resend-mails
createSiteMailerV1MailerResendMails → 200401404default
POST
/site-mailer/v1/mailer/send-test-mail
POST /site-mailer/v1/mailer/send-test-mail
createSiteMailerV1MailerSendTestMail → 200401404default
POST
/site-mailer/v1/reviews/review
POST /site-mailer/v1/reviews/review
createSiteMailerV1ReviewsReview → 200401404default
GET
/site-mailer/v1/settings/get-settings
GET /site-mailer/v1/settings/get-settings
getSiteMailerV1SettingsGetSettings → 200401404default
GET
/site-mailer/v1/statuses/get-stats
GET /site-mailer/v1/statuses/get-stats
getSiteMailerV1StatusesGetStats → 200401404default
GET
/site-mailer/v1/statuses/get-statuses
GET /site-mailer/v1/statuses/get-statuses
getSiteMailerV1StatusesGetStatuses → 200401404default
POST
/site-mailer/v1/suppressions/add-suppression
POST /site-mailer/v1/suppressions/add-suppression
createSiteMailerV1SuppressionsAddSuppression → 200401404default
DELETE
/site-mailer/v1/suppressions/delete-suppressions
DELETE /site-mailer/v1/suppressions/delete-suppressions
deleteSiteMailerV1SuppressionsDeleteSuppressions → 200401404default
GET
/site-mailer/v1/suppressions/get-suppressions
GET /site-mailer/v1/suppressions/get-suppressions
getSiteMailerV1SuppressionsGetSuppressions → 200401404default
GET
/site-mailer/v1/suppressions/unsubscribe/{email}
GET /site-mailer/v1/suppressions/unsubscribe/{email}
getSiteMailerV1SuppressionsUnsubscribeEmail 1 param → 200401404default
POST
/site-mailer/v1/suppressions/unsubscribe/{email}
POST /site-mailer/v1/suppressions/unsubscribe/{email}
createSiteMailerV1SuppressionsUnsubscribeEmail 1 param → 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-site-mailer-v1-api-openapi.yml Raw ↑

Other APIs Ascend Elements publishes across the network.

Ascend Elements Complianz/v1 API
AE Profile APIs.io
Ascend Elements Core API
AE Profile APIs.io
Ascend Elements Cptui/v1 API
AE Profile APIs.io
Ascend Elements Ea11y/v1 API
AE Profile APIs.io
Ascend Elements Elementor Ai/v1 API
AE Profile APIs.io
Ascend Elements Elementor One/v1 API
AE Profile APIs.io
Ascend Elements Elementor Pro/v1 API
AE Profile APIs.io
Ascend Elements Elementor/v1 API
AE Profile APIs.io
Ascend Elements Elementor/v1/documents API
AE Profile APIs.io
Ascend Elements Elementor/v1/feedback API
AE Profile APIs.io
Ascend Elements Facetwp/v1 API
AE Profile APIs.io
Ascend Elements Image Optimizer/v1 API
AE Profile APIs.io
#site-mailer/v1
← Back to A APIs
API Details
ID
ascend-elements:ascend-elements-site-mailer-v1-api
Base URL
https://ascendelements.com/wp-json
Docs
https://ascendelements.com/wp-json/
Provider
Ascend Elements
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=ascend-elements-site-mailer-v1-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/ascend-elements-site-mailer-v1-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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