# Create Email Forwarding

Creates a new email forwarding rule for a domain, such as redirecting info@example.com to an external inbox.  If this is the first email forwarding rule created for the domain, the API may also update your MX records automatically to enable mail routing.  The alias must not conflict with existing email services or MX records.  To modify a forwarding rule later, use UpdateEmailForwarding.

Endpoint: POST /core/v1/domains/{domainName}/email/forwarding
Version: 1.3.1
Security: BasicAuth

## Path parameters:

  - `domainName` (string, required)
    DomainName is the domain part of the email address to forward.
    Example: "example.com"

## Request fields (application/json):

  - `emailBox` (string, required)
    EmailBox is the user portion of the email address to forward. If your email is "admin@example.com", it would just be "admin"
    Example: "admin"

  - `emailTo` (string, required)
    EmailTo is the entire email address to forward email to.
    Example: "webmaster@example.com"

## Response 200 fields (application/json):

  - `domainName` (string, required)
    DomainName is the domain part of the email address to forward.
    Example: "example.com"

  - `emailBox` (string, required)
    EmailBox is the user portion of the email address to forward.
    Example: "admin"

  - `emailTo` (string, required)
    EmailTo is the entire email address to forward email to.
    Example: "webmaster@example.com"

## Response 400 fields (application/json):

  - `message` (string)
    A human-readable message providing more details about the error
    Example: "Bad Request"

  - `details` (string,null)
    Additional context or information about the error
    Example: "'domainName' cannot be null"

## Response 403 fields (application/json):

  - `message` (string)
    Example: "Permission Denied. The domain is expired."

## Response 415 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error
    Example: "The 'Content-Type' header must be 'application/json' for this request."

## Response 429 fields (application/json):

  - `message` (string)
    A human-readable message providing more details about the error
    Example: "Rate Limit Exceeded"

## Response 500 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error.
    Example: "Internal Server Error"

  - `details` (string,null)
    Additional context or information about the error.
    Example: "Something went wrong."