Skip to main content
curl --request POST \
  --url https://api.autosend.com/v1/domains/60d5ec49f1b2c72d9c8b1111/inbound/enable \
  --header 'Authorization: Bearer <token>'

{
  "success": true,
  "data": {
    "id": "60d5ec49f1b2c72d9c8b1111",
    "domainName": "example.com",
    "verificationStatus": "VERIFIED",
    "ownershipVerified": true,
    "dkimEnabled": true,
    "mailFromEnabled": true,
    "dmarcEnabled": true,
    "dnsRecords": {
      "inboundMx": {
        "name": "example.com",
        "value": "inbound-smtp.us-east-1.amazonaws.com",
        "type": "MX",
        "purpose": "inbound",
        "priority": 10
      }
    },
    "createdAt": "2026-01-05T10:00:00.000Z",
    "lastCheckedAt": "2026-03-10T14:20:00.000Z",
    "verifiedAt": "2026-01-05T12:00:00.000Z",
    "regionKey": "us-east-1",
    "verificationInProgress": false,
    "inboundEnabledAt": "2026-03-10T14:25:00.000Z",
    "inboundDomainVerifiedAt": null
  }
}
Enable inbound email receiving on a custom domain that has already been verified. Calling this endpoint stamps the domain as inbound-enabled and returns the inbound MX record you must publish in your DNS. Once that MX record is detected in DNS during the next verification check, AutoSend wires up the SES receipt rule and inbound becomes live for the domain (at which point inboundDomainVerifiedAt is set).

​
Authorizations

​
Authorization
string | header
required
Bearer authentication header of the form Bearer <token>, where <token> is your API key.

​
Path Parameters

​
domainId
string
required
The id of the domain on which to enable inbound receiving.

​
Response

​
success
boolean
Indicates whether the request was successful.
​
data
object
The updated domain object.

​
Errors

​
404
object
Returned when no domain with the given domainId exists in the project.
​
500
object
Returned when inbound receiving could not be enabled on the domain.