Properties
| Name | Type | Description |
|---|---|---|
| meta | object | |
| ok | boolean | |
| data | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/sendmux-ai/json-schema/sendmux-ai-domain-verify-response-schema.json",
"title": "DomainVerifyResponse",
"x-generated": "2026-11-10",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/sendmux-ai-domains-api-openapi.yml#/components/schemas/DomainVerifyResponse",
"allOf": [
{
"$ref": "#/$defs/SuccessEnvelope"
},
{
"properties": {
"data": {
"$ref": "#/$defs/MailboxDomainVerifyResult"
},
"meta": {
"$ref": "#/$defs/ResponseMeta"
}
},
"required": [
"data"
],
"type": "object"
}
],
"unevaluatedProperties": false,
"$defs": {
"MailboxDomainVerifyChecks": {
"additionalProperties": false,
"properties": {
"dmarc": {
"description": "A DMARC record containing v=DMARC1 is present.",
"type": "boolean"
},
"mail_from_mx": {
"description": "Custom MAIL FROM MX record matches expected value",
"type": "boolean"
},
"mail_from_spf": {
"description": "Custom MAIL FROM SPF policy is compatible with the required Amazon SES sender authorisation.",
"type": "boolean"
},
"mx": {
"description": "MX record present when the domain is configured for receiving. Always true for send-only domains.",
"type": "boolean"
},
"spf": {
"description": "Published SPF policy is compatible with the required Amazon SES sender authorisation.",
"type": "boolean"
},
"verification_txt": {
"description": "Ownership TXT record present with correct value",
"type": "boolean"
}
},
"required": [
"mx",
"verification_txt",
"spf",
"dmarc",
"mail_from_mx",
"mail_from_spf"
],
"type": "object"
},
"MailboxDomainVerifyResult": {
"additionalProperties": false,
"properties": {
"checks": {
"$ref": "#/$defs/MailboxDomainVerifyChecks"
},
"ses_dkim_signing_enabled": {
"description": "Whether Amazon SES DKIM signing is enabled",
"type": "boolean"
},
"ses_dkim_status": {
"description": "Latest Amazon SES DKIM status",
"type": "string"
},
"ses_identity_checked_at": {
"description": "ISO 8601 time of this SES identity check",
"type": "string"
},
"ses_identity_verification_status": {
"description": "Latest Amazon SES identity status",
"type": "string"
},
"ses_mail_from_status": {
"description": "Latest Amazon SES MAIL FROM status",
"type": "string"
},
"ses_verified_for_sending": {
"description": "Whether Amazon SES permits identity sending",
"type": "boolean"
},
"status": {
"description": "Post-check verification status",
"enum": [
"verified",
"pending",
"failed"
],
"type": "string"
}
},
"required": [
"status",
"ses_identity_verification_status",
"ses_verified_for_sending",
"ses_dkim_status",
"ses_dkim_signing_enabled",
"ses_identity_checked_at",
"ses_mail_from_status",
"checks"
],
"type": "object"
},
"ResponseMeta": {
"additionalProperties": false,
"properties": {
"request_id": {
"type": "string"
}
},
"required": [
"request_id"
],
"type": "object"
},
"SuccessEnvelope": {
"properties": {
"meta": {
"additionalProperties": {},
"properties": {},
"type": "object"
},
"ok": {
"enum": [
true
],
"type": "boolean"
}
},
"required": [
"ok",
"meta"
],
"type": "object"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/sendmux-ai-domain-verify-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API 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.