Reach: Profiles

Connect sending domain

Changed on

Connect a sending domain to the profile so emails can be sent from addresses on it.

Connecting does not make the domain ready to send: check the DNS status endpoint next for records that are still missing. A domain the account owns or has already verified connects immediately. Any other domain starts a TXT ownership verification and returns 409; complete the verification in Reach, then retry. Returns 422 when the profile or another profile already has the domain, the domain is blocked, or its ownership cannot be verified. An already connected domain is never replaced.

On success the sender address of draft and scheduled campaigns, and of published automation and double opt-in emails, moves onto the new domain in the background, keeping the part before the @.

post/api/reach/v1/profiles/{profileUuid}/domains

Request

  • Base URL: https://developers.hostinger.com
  • URL: https://developers.hostinger.com/api/reach/v1/profiles/{profileUuid}/domains
  • Auth: HTTP bearer

Path parameters

profileUuidstring required
Example:550e8400-e09b-41d4-a716-400055000000

Profile uuid parameter

Request body

domainstring required

Example request

{
  "domain": "example.com"
}

Response

Success empty response

messagestring

Example response

{
  "message": "Request accepted"
}

Changes