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

ClickFunnels Emails::Domain API

> Email Domains represent the sending domains (DKIM/SPF/DMARC) available to a workspace for outbound email.One domain name has two independent jobs, and sending needs both. This resource covers email transport: `verified` means the name is authenticated for sending (DKIM + SPF + DMARC, or a verified SMTP setting). The other job is proving the workspace owns the name, reported here as `ownership_verified`; that happens by connecting the domain to the workspace as a website/hosting domain inside the ClickFunnels app (a website domain is connected as a subdomain such as `www.example.com`, which confirms ownership of the root sending domain `example.com`), and no call in this API can make it true. Neither substitutes for the other: `ready_for_sending` becomes true only when both are true, and a `200` from verify means the check ran, not that it passed, so always read the booleans back.Provision the root domain (`example.com`), not a subdomain: ownership is confirmed at the root domain, so a subdomain is rejected with `422` naming the root domain to use instead.Typical workflow: provision the sending domain (`POST /workspaces/{workspace_id}/emails/domains`), have the customer publish the returned DNS records and connect the same name to the workspace in ClickFunnels, then re-check with `POST /emails/domains/{id}/verify` until `ready_for_sending` is true, following `next_steps` for whatever is still missing. Then create sender addresses via `POST /workspaces/{workspace_id}/emails/addresses` with `emails_domain_id` set to this domain's numeric id.See [Sending domains](https://accounts.myclickfunnels.com/.well-known/emails/skill.md#sending-domains) in the [Emails Skill](https://accounts.myclickfunnels.com/.well-known/emails/skill.md).

ClickFunnels Emails::Domain API is one of 102 APIs that ClickFunnels publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Emails::Domain. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and rate-limit docs.

This API exposes 4 operations across 3 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://{subdomain}.myclickfunnels.com/api/v2.

4 operations 3 paths 3 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://{subdomain}.myclickfunnels.com/api/v2
Authentication
HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 1

ClickFunnels Emails::Domain API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Emails::Domain 4

Email Domains represent the sending domains (DKIM/SPF/DMARC) available to a workspace for outbound email. One domain name has two independent jobs, and sending needs both. This re…

GET
/workspaces/{workspace_id}/emails/domains
List Email Domains
listEmailsDomains 4 params → 200401404
POST
/workspaces/{workspace_id}/emails/domains
Create Email Domain
createEmailsDomains 1 param body → 200201401403404422
GET
/emails/domains/{id}
Get Email Domain
getEmailsDomains 1 param → 200401404
POST
/emails/domains/{id}/verify
Verify Email Domain
verifyEmailsDomains 1 param → 200401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are EmailsDomainAttributes (19 properties), DnsRecord (5 properties), EmailsDomainParameters (1 property). Each schema is shown below with its type and property counts.

EmailsDomainParameters
object
A sending domain to provision for a workspace.
1 property 1 required
EmailsDomainAttributes
object
Email Domains
19 properties 19 required
DnsRecord
object
A single DNS record to add at the domain's DNS provider to configure email transport (or, for the return path, bounce handling).
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

clickfunnels-emails-domain-api-openapi.yml Raw ↑

Other APIs ClickFunnels publishes across the network.

ClickFunnels Addresses::Country API
ClickFunnels Addresses::Region API
ClickFunnels Appointments::Scheduled Event API
ClickFunnels Blog API
ClickFunnels Blogs::Author API
ClickFunnels Blogs::Category API
ClickFunnels Blogs::Post API
ClickFunnels Blogs::Tag API
ClickFunnels Communities::Ban API
ClickFunnels Communities::Bans::Export Action API
ClickFunnels Communities::Bans::Unban Action API
ClickFunnels Communities::Membership API
Where this information came from

This is an independent, third-party profile of ClickFunnels Emails::Domain 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.