Skip to main content
POST
Create IPPool

Authorizations

X-Account-ApiKey
string
header
required

This api key can be used for all account level operations

Body

application/json

Request body for creating a new IP pool

name
string
required

Display name for the IP pool. Must be unique within your account. Use descriptive names like "transactional", "marketing-bulk", "high-priority"

Required string length: 1 - 100
Example:

"Marketing Promotional"

ips
object[]

List of dedicated IP addresses to include in this pool. IPs must already be allocated to your account.

tpsps
integer<int64>[]

List of third-party sending provider IDs to include in this pool. TPSPs must be pre-configured in your account.

Example:
routingStrategy
enum<integer>
default:0

Email routing strategy:

  • 0 = Round Robin (equal distribution)
  • 1 = Email Provider Strategy (route by recipient domain)
  • 2 = Volume Percentage Strategy (weighted distribution)
  • 3 = Sending Domain Strategy (route by sender domain)
Available options:
0,
1,
2,
3
Example:

0

routingMetaData
string
default:{}

JSON-encoded routing configuration. See IPPools documentation for format. Use {} for round-robin strategy.

Example:

"{}"

shouldOverflow
boolean
default:false

Whether to overflow to shared pool when this pool is unavailable

Example:

true

overflowPoolName
string

Name of the IP pool to overflow to (if shouldOverflow is true)

Example:

"shared-backup"

Response

Created IPPool details

An IP Pool groups one or more dedicated IPs and/or third-party sending providers for email delivery. Use IP pools to:

  • Separate transactional vs marketing email reputation
  • Route emails based on recipient domain (Gmail, Yahoo, etc.)
  • Implement volume-based routing strategies
  • Configure failover to backup providers

When sending email, specify the ippool parameter to route through a specific pool.

id
integer<int64>

Unique identifier for the IP pool

Example:

746

name
string

Display name for the IP pool. Must be unique within your account. Use descriptive names like "transactional", "marketing", "high-priority".

Maximum string length: 100
Example:

"Transactional"

type
enum<integer>

Type of IP pool:

  • 0 = Shared (uses shared IPs with pooled reputation)
  • 1 = Dedicated (uses dedicated IPs exclusive to your account)
Available options:
0,
1
Example:

1

routingStrategy
enum<integer>

How emails are distributed across IPs/providers in this pool:

  • 0 = Round Robin (equal distribution)
  • 1 = Email Provider Strategy (route by recipient domain like Gmail, Yahoo)
  • 2 = Volume Percentage Strategy (weighted distribution)
  • 3 = Sending Domain Strategy (route by sender domain)

See the IPPools tag description for detailed routing configuration examples.

Available options:
0,
1,
2,
3
Example:

0

routingMetaData
string

JSON-encoded configuration for the selected routing strategy. Format depends on routingStrategy value. See IPPools documentation for examples.

For Round Robin (strategy 0): Use empty object {}

Example:

"{}"

shouldOverflow
boolean

Whether to automatically overflow to a backup pool when this pool is unavailable (all IPs down) or at capacity (warmup limits reached).

Example:

true

overflowPoolName
string

Name of the IP pool to overflow to when shouldOverflow is enabled. The overflow pool must exist. Common pattern: overflow to shared IP pool.

Example:

"shared-backup"

ips
object[]

List of dedicated IPs assigned to this pool

created
integer<int64>

UNIX epoch timestamp in nanoseconds when the IP pool was created

Example:

1704067200000000000