Skip to main content
POST
/
inbound
/
domains
/
{uuid}
/
forward-rules
curl --request POST \
  --url https://api.jetemail.com/inbound/domains/{uuid}/forward-rules \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "localpart": "support",
  "destination": "team@theirinbox.com"
}
'
{
  "success": true,
  "result": {
    "uuid": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "localpart": "<string>",
    "destination": "jsmith@example.com",
    "active": 0,
    "verified": 0,
    "last_modified": 123,
    "created_at": 123
  }
}

Documentation Index

Fetch the complete documentation index at: https://jetemail.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

API key for account management endpoints. Use your api_ prefixed token.

Path Parameters

​
uuid
string<uuid>
required

UUID of the domain

Pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$

Body

application/json
​
localpart
string
required

Address prefix to match. Use the literal "*" for catch-all. Otherwise must be a valid RFC 5321 local-part (max 64 chars). Stored lowercased; plus-addressing is handled at match time, so a rule for "support" also matches "support+anything".

Example:

"support"

​
destination
string<email>
required

Bare email address (local@domain). No display names, no quoted local-parts.

Example:

"team@theirinbox.com"

​
active
boolean
default:true

Inactive rules are stored but ignored at RCPT TO. Use this for soft-disable rather than DELETE if you plan to re-enable.

Response

Rule created

​
success
boolean
Example:

true

​
result
object