Conduyt Email Domains API
Custom email domain verification (Resend)
Custom email domain verification (Resend)
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/conduyt-com:conduyt-com-email-domains-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Conduyt Email Domains API
version: 1.0.0
description: 'The Conduyt CRM API provides programmatic access to your CRM data including
contacts, companies, deals, pipelines, tasks, notes, automations, invoices,
email sequences, and more.
## Authentication
All authenticated endpoints require a Bearer token (API key) in the
`Authorization` header:
```
Authorization: Bearer cdy_
```
API keys are generated in **Settings > API Keys** within the Conduyt
dashboard. Keys use the `cdy_` prefix and are hashed with bcrypt on
creation — the full key is shown exactly once at creation time.
Session cookie authentication (`conduyt_session`) is also supported for
browser-based clients but is not recommended for integrations.
## Rate Limiting
API keys enforce a per-key rate limit. New keys default to 100 requests per
minute and can be configured at creation time or with PATCH `/api-keys/{id}`.
Some public and provider-facing endpoints also enforce stricter per-IP or
per-account limits. When exceeded, the API returns `429 Too Many Requests`
with a `Retry-After` header indicating seconds until the next allowed
request.
| Endpoint Group | Limit |
|---------------------|---------------------|
| API keys | Default 100 / min per key |
| Login/reset | 5 / min per IP |
| Registration | 3 / hour per IP |
| Contact/Deal create | 30 / min per IP |
| Inbound messages | 120 / min per account/IP |
## Pagination
List endpoints support cursor-based pagination via query parameters:
- `page` — Page number (default: 1)
- `per_page` — Items per page (default: 50, max: 200)
- `limit` — Accepted as an alias of `per_page` on `GET /contacts`; if both are
sent they must carry the same value.
A page size above the maximum, a non-integer, a value below 1, or a
pagination key repeated with different values is rejected with `400`
(the message names the parameter and the rule); nothing is silently
clamped or ignored.
Responses include a `meta` object: `{ page, per_page, total }`.
An operation that documents its own pagination rules follows those instead.
`GET /sms-providers/options` pages with an opaque `cursor` and a `limit`
that is capped at 50 rather than rejected; its responses carry
`meta: { nextCursor, truncated }`.
## Response Format
All successful responses wrap data in a `data` envelope:
```json
{ "data": { ... } }
```
Error responses use:
```json
{ "error": "Human-readable error message" }
```
## Multi-Tenancy
Conduyt is multi-tenant. All data is scoped to the authenticated user''s
current account. API keys are bound to a specific account at creation time.
## Webhook Events
Outbound webhooks fire on events including:
`contact.created`, `contact.updated`, `contact.deleted`,
`deal.created`, `deal.updated`, `deal.won`, `deal.lost`,
`task.created`, `task.completed`, `note.created`,
`appointment.created`, `appointment.updated`,
`form.submitted`, `invoice.paid`
Payloads are signed with HMAC-SHA256 using the webhook''s secret. Retry
schedule: 1m, 5m, 30m, 2h, 12h, 72h (7 total attempts including the initial delivery).'
contact:
name: Conduyt Support
url: https://conduyt.app
email: support@conduyt.app
license:
name: Proprietary
url: https://conduyt.app/terms
servers:
- url: https://conduyt.app/api/v1
description: Production
security:
- BearerAuth: []
tags:
- name: Email Domains
description: Custom email domain verification (Resend)
paths:
/email-domains:
get:
operationId: getEmailDomain
summary: Get email domain configuration
tags:
- Email Domains
responses:
'200':
description: Email domain details with DNS records
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
usage: {}
extraDomains: {}
domainAllowance: {}
required:
- usage
- extraDomains
- domainAllowance
required:
- data
parameters: []
post:
operationId: addEmailDomain
summary: Add a custom email domain
tags:
- Email Domains
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- domain
properties:
domain:
type: string
fromAddress:
type: string
fromName:
type: string
responses:
'200':
description: Domain added with DNS records to configure
content:
application/json:
schema:
$ref: '#/components/schemas/DataEnvelope'
'201':
description: Created
x-generated-status: true
content:
application/json:
schema:
$ref: '#/components/schemas/DataEnvelope'
parameters: []
patch:
operationId: updateEmailDomain
summary: Update email domain settings
tags:
- Email Domains
responses:
'200':
description: Email domain updated
content:
application/json:
schema:
$ref: '#/components/schemas/DataEnvelope'
parameters: []
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
domainId:
description: Read by the handler from the JSON body (the route declares no schema for its type).
fromAddress:
description: Read by the handler from the JSON body (the route declares no schema for its type).
fromName:
description: Read by the handler from the JSON body (the route declares no schema for its type).
delete:
operationId: removeEmailDomain
summary: Remove email domain
tags:
- Email Domains
responses:
'200':
description: Email domain removed
content:
application/json:
schema:
$ref: '#/components/schemas/DataEnvelope'
parameters:
- name: domainId
in: query
required: false
description: Query parameter read by this route.
schema:
type: string
requestBody:
required: false
content:
application/json:
schema:
type: object
properties:
domainId:
description: Read by the handler from the JSON body (the route declares no schema for its type).
/email-domains/verify:
post:
operationId: verifyEmailDomain
summary: Verify DNS configuration for email domain
tags:
- Email Domains
responses:
'200':
description: Verification result
content:
application/json:
schema:
$ref: '#/components/schemas/DataEnvelope'
parameters: []
requestBody:
required: false
content:
application/json:
schema:
type: object
properties:
domainId:
description: Read by the handler from the JSON body (the route declares no schema for its type).
/email-domains/status:
get:
x-generated: true
operationId: getEmailDomainsStatus
summary: List email-domains status
tags:
- Email Domains
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
domain: {}
status: {}
verified: {}
fromAddress: {}
fromName: {}
fromPreview: {}
required:
- domain
- status
- verified
- fromAddress
- fromName
- fromPreview
required:
- data
/email-domains/reply-capture/verify:
post:
x-generated: true
operationId: postEmailDomainsReplyCaptureVerify
summary: Create / invoke email-domains reply-capture verify
tags:
- Email Domains
responses:
'200':
description: Success
content:
application/json:
schema:
oneOf:
- type: object
properties:
data:
type: object
properties:
verified:
type: boolean
providerStatus: {}
dnsRecords: {}
pending: {}
required:
- verified
- providerStatus
- dnsRecords
- pending
required:
- data
- type: object
properties:
data:
type: object
properties:
verified:
type: boolean
configured:
type: boolean
domain: {}
address: {}
dnsRecords: {}
required:
- verified
- configured
- domain
- address
- dnsRecords
required:
- data
/email-domains/reply-capture:
delete:
x-generated: true
operationId: deleteEmailDomainsReplyCapture
summary: Delete email-domains reply-capture
tags:
- Email Domains
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
removed:
type: boolean
wasLive:
type: boolean
cleanupCompleted:
type: boolean
providerCleanup:
type: string
draining:
type: boolean
drainEndsAt: {}
deliveryGuaranteed: {}
message: {}
required:
- removed
- wasLive
required:
- data
get:
x-generated: true
operationId: getEmailDomainsReplyCapture
summary: List email-domains reply-capture
tags:
- Email Domains
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
configured:
type: boolean
needsSupport:
type: boolean
domain: {}
address: {}
verified:
type: boolean
providerStatus:
type: string
dnsRecords: {}
pending: {}
degraded:
type: boolean
repair:
type: string
health:
type: string
healthWarning:
type: string
cleanupPending: {}
cleanupDomain: {}
suggestedDomain: {}
required:
- data
post:
x-generated: true
operationId: postEmailDomainsReplyCapture
summary: Create / invoke email-domains reply-capture
tags:
- Email Domains
requestBody:
required: false
content:
application/json:
schema:
type: object
properties:
domain:
description: Read by the handler from the JSON body (the route declares no schema for its type).
responses:
'201':
description: Created
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
configured:
type: boolean
verified:
type: boolean
pending: {}
dnsRecords: {}
providerStatus: {}
required:
- configured
- verified
- pending
- dnsRecords
- providerStatus
required:
- data
components:
schemas:
DataEnvelope:
type: object
properties:
data:
description: Response payload (shape varies by endpoint)
securitySchemes:
BearerAuth:
type: http
scheme: bearer
description: 'API key authentication. Generate keys in Settings > API Keys.
Keys use the `cdy_` prefix.
Example: `Authorization: Bearer cdy_a1b2c3d4e5f6...`
'
x-mcp:
transport:
- stdio
- http
orchestration: code
endpoint_tools: hidden