MepMail · Schema

GetDomainResponse

EmailServicesCommunicationsDevelopers

Properties

Name Type Description
id string
name string
status string
created_at string
region string
open_tracking boolean
click_tracking boolean
tracking_subdomain stringnull
capabilities object
object string
records array
View JSON Schema on GitHub

JSON Schema

mepmail-dev-get-domain-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/mepmail-dev/json-schema/mepmail-dev-get-domain-response-schema.json",
  "title": "GetDomainResponse",
  "x-generated": "2026-11-18",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/mepmail-dev-api-openapi.json#/components/schemas/GetDomainResponse",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "format": "uuid"
    },
    "name": {
      "type": "string"
    },
    "status": {
      "type": "string"
    },
    "created_at": {
      "type": "string"
    },
    "region": {
      "type": "string"
    },
    "open_tracking": {
      "type": "boolean"
    },
    "click_tracking": {
      "type": "boolean"
    },
    "tracking_subdomain": {
      "type": [
        "string",
        "null"
      ]
    },
    "capabilities": {
      "type": "object",
      "properties": {
        "sending": {
          "type": "string"
        },
        "receiving": {
          "type": "string"
        }
      },
      "required": [
        "sending",
        "receiving"
      ]
    },
    "object": {
      "type": "string",
      "enum": [
        "domain"
      ]
    },
    "records": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "record": {
            "type": "string",
            "description": "Which record this is: DKIM, SPF (the MAIL FROM MX and TXT rows), DMARC, or Tracking (the branded tracking CNAME, present once a tracking subdomain is set). Only the DKIM and SPF rows gate sending."
          },
          "name": {
            "type": "string"
          },
          "type": {
            "type": "string"
          },
          "ttl": {
            "type": "string"
          },
          "status": {
            "type": "string",
            "description": "not_started | pending | verified | failed. DKIM and SPF rows combine public DNS with the provider's verification: found in DNS but not yet confirmed reads pending, a different published value reads failed, no record reads not_started. DMARC reads verified when a policy covers the domain — its own or a parent domain's (see inherited_from) — and not_started when none does. Tracking reads verified once its CNAME resolves."
          },
          "value": {
            "type": "string"
          },
          "priority": {
            "type": "number"
          },
          "live": {
            "type": "string",
            "enum": [
              "found",
              "missing",
              "mismatch",
              "unknown"
            ],
            "description": "What public DNS answers for this record right now: found, missing, mismatch (a different value is published) or unknown (the lookup did not conclude). Omitted when no live check ran (the create response)."
          },
          "detail": {
            "type": "string",
            "description": "One sentence explaining a row that is not verified: found but awaiting the provider, the value that is published instead, no record at the name, or which parent DMARC policy covers the domain. Omitted when there is nothing to add."
          },
          "inherited_from": {
            "type": "string",
            "description": "DMARC only: the _dmarc name whose policy covers this domain when it has no record of its own (RFC 7489 organizational-domain fallback)."
          },
          "policy": {
            "type": "string",
            "enum": [
              "none",
              "quarantine",
              "reject"
            ],
            "description": "DMARC only, alongside inherited_from: the inherited policy's p= value."
          }
        },
        "required": [
          "record",
          "name",
          "type",
          "ttl",
          "status",
          "value"
        ]
      }
    }
  },
  "required": [
    "id",
    "name",
    "status",
    "created_at",
    "region",
    "open_tracking",
    "click_tracking",
    "tracking_subdomain",
    "capabilities",
    "object",
    "records"
  ]
}

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.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/mepmail-dev-get-domain-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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

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