> For the complete documentation index, see [llms.txt](https://docs.mailtrap.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mailtrap.io/developers/email-sending/domains/create-domain.md).

# Create domain

Create a domain for email authentication. After creation, verify the domain by adding DNS records.

**Process:**

1. Create the domain
2. Add DNS records (SPF, DKIM, DMARC)
3. Verify the records
4. Start sending emails

```json
{"openapi":"3.1.0","info":{"title":"Email Sending","version":"2.0.0"},"tags":[{"name":"domains","description":"Configure and verify domains for email sending to ensure deliverability.\n"}],"servers":[{"description":"Mailtrap account API (`mailtrap.io`) for domains, suppressions, tracking opt-outs, stats, and email logs.\nError JSON matches other account endpoints (`error` or string `errors`), not the `send.api` / `bulk.api` sending shape (`success` + `errors` array).\n","url":"https://mailtrap.io"}],"security":[{"HeaderAuth":[]},{"BearerAuth":[]}],"components":{"securitySchemes":{"HeaderAuth":{"type":"apiKey","description":"API token in Api-Token header","in":"header","name":"Api-Token"},"BearerAuth":{"type":"http","scheme":"bearer","bearerFormat":"JWT","description":"Bearer token authentication"}},"responses":{"DomainResponse":{"description":"Domain details","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Domain"}}}},"Unauthorized":{"description":"Returns unauthorized error message. Check your credentials.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/UnauthenticatedResponse"}}}},"Forbidden":{"description":"Returns forbidden error message. Check your permissions.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/PermissionsDeniedResponse"}}}},"UnprocessableEntity":{"description":"Validation errors","content":{"application/json":{"schema":{"$ref":"#/components/schemas/UnprocessableEntity"}}}}},"schemas":{"Domain":{"type":"object","properties":{"id":{"type":"integer"},"domain_name":{"type":"string"},"demo":{"type":"boolean"},"compliance_status":{"type":"string","description":"Indicates the compliance verification status of the domain.\nThe domain must reach `compliant` status before you can send emails\nin production.\n\n- `demo` - A demo domain provided by Mailtrap. Can only send emails to the account owner.\n- `demo_exhausted` - A demo domain that has used up its sending allowance. Cannot send emails.\n- `unverified_dns` - Domain DNS records have not been verified yet. Open your domain on the [Domains](https://mailtrap.io/domains) page and follow the [Sending Domain Setup](https://docs.mailtrap.io/email-api-smtp/setup/sending-domain) guide.\n- `missing_company_info` - Account is missing required company information. Go to [Company Information](https://mailtrap.io/settings/account?current_tab=company_information) and fill in the required details.\n- `under_review` - Domain is undergoing automatic compliance review. No action needed — typically completes within 2 minutes.\n- `awaiting_questionnaire` - Automatic review required additional information. Open your domain on the [Domains](https://mailtrap.io/domains) page and fill in the compliance questionnaire.\n- `awaiting_card_verification` - Compliance questionnaire was submitted but credit card identity verification is still needed. Open your domain on the [Domains](https://mailtrap.io/domains) page and enter card details. The charged amount is refunded immediately and the card is not stored.\n- `non_compliant` - Domain did not pass compliance checks. Sending is not allowed. Contact [Mailtrap Support](mailto:support@mailtrap.io) for details and next steps.\n- `compliant` - Domain has passed all compliance checks and is ready to send emails.\n- `suspended` - Domain sending has been suspended. Contact [Mailtrap Support](mailto:support@mailtrap.io) to resolve the issue.\n","enum":["demo","demo_exhausted","unverified_dns","missing_company_info","under_review","awaiting_questionnaire","awaiting_card_verification","non_compliant","compliant","suspended"]},"dns_verified":{"type":"boolean"},"dns_verified_at":{"type":["string","null"]},"dns_records":{"type":"array","items":{"type":"object","properties":{"key":{"type":"string"},"domain":{"type":"string"},"name":{"type":"string"},"status":{"type":"string","enum":["pass","fail","unchecked","missing","softfail","network_error"]},"type":{"type":"string"},"value":{"type":"string"}}}},"open_tracking_enabled":{"type":"boolean"},"click_tracking_enabled":{"type":"boolean"},"tracking_opt_out_enabled":{"type":"boolean","description":"When enabled, recipients can opt out of open and click tracking via a link in tracked emails.\nRequires open or click tracking to be enabled.\n"},"auto_unsubscribe_link_enabled":{"type":"boolean"},"custom_domain_tracking_enabled":{"type":"boolean"},"health_alerts_enabled":{"type":"boolean"},"critical_alerts_enabled":{"type":"boolean"},"alert_recipient_email":{"type":["string","null"]},"inbound_enabled":{"type":"boolean","description":"Whether inbound email is enabled for this domain. When enabled, an\n`MX` record (`key: inbound_mx`) is added to `dns_records` for inbound\nmail; see `inbound_verified`.\n"},"inbound_verified":{"type":"boolean","description":"Whether the domain's inbound MX records have been verified. Inbound\nmail is only accepted once this is `true`.\n"},"permissions":{"type":"object","properties":{"can_read":{"type":"boolean"},"can_update":{"type":"boolean"},"can_destroy":{"type":"boolean"}}}}},"UnauthenticatedResponse":{"title":"UnauthenticatedResponse","type":"object","properties":{"error":{"type":"string","description":"Error message"}}},"PermissionsDeniedResponse":{"title":"PermissionsDeniedResponse","type":"object","properties":{"errors":{"type":"string","description":"Error message"}}},"UnprocessableEntity":{"type":"object","description":"Validation errors per field. Keys are attribute names; values are arrays of human-readable messages.\nSome endpoints may also return a `base` key with general validation errors.","properties":{"errors":{"type":"object","additionalProperties":{"type":"array","items":{"type":"string"}}}}}}},"paths":{"/api/domains":{"post":{"summary":"Create domain","description":"Create a domain for email authentication. After creation, verify the domain by adding DNS records.\n\n**Process:**\n1. Create the domain\n2. Add DNS records (SPF, DKIM, DMARC)\n3. Verify the records\n4. Start sending emails\n","operationId":"createDomain","tags":["domains"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"type":"object","required":["domain"],"properties":{"domain":{"type":"object","required":["domain_name"],"properties":{"domain_name":{"type":"string","format":"hostname","description":"Your domain name"}}}}}}}},"responses":{"200":{"$ref":"#/components/responses/DomainResponse"},"401":{"$ref":"#/components/responses/Unauthorized"},"403":{"$ref":"#/components/responses/Forbidden"},"422":{"$ref":"#/components/responses/UnprocessableEntity"}}}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mailtrap.io/developers/email-sending/domains/create-domain.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.