Dedicated IP Addresses Now Available for Email API

The Telnyx Email API now supports dedicated sending IPs for eligible verified and enterprise customers, reducing exposure to other customers’ IP-level reputation. Deliverability still depends on the sender’s sending practices and recipient mailbox-provider policies.

What's new

• Dedicated sending IPs: Purchase and manage an account-owned sending IP instead of using the shared IP pool.
• Reputation isolation: Your IP reputation reflects your own traffic rather than aggregate shared-pool traffic.
• Warm-up and routing controls: Provision an IP, manage its warm-up, and route sending through account- or domain-scoped IP pools.
• Status visibility: Monitor provisioning, DNS, pool assignment, and warm-up state through the Dedicated IP API.

Why it matters

Shared IP pools work well for most senders, but the largest email programs need more control. When you share an IP with thousands of other senders, your deliverability depends on their behavior too. One bad actor on a shared IP can trigger rate limits or blocklists that affect everyone.

A dedicated IP separates your IP-level reputation from other customers’ shared-pool traffic, allowing your sending practices and warm-up strategy to shape that reputation directly. This gives sophisticated email programs the control they need to optimize inbox placement. Domain reputation, message quality, engagement, and mailbox-provider policies still affect delivery outcomes.

Example use cases

• High-volume transactional senders delivering millions of messages per month who need consistent deliverability.
• Enterprise email programs with dedicated deliverability teams monitoring IP reputation and sending patterns.
• Marketing teams running large campaigns where sender reputation directly impacts campaign ROI.

Getting started

• Purchase an IP with POST /v2/email/dedicated_ips.
• Start IP warm-up with POST /v2/email/dedicated_ips/{id}/actions/start_warmup.
• Create an IP pool with POST /v2/email/ip_pools, optionally setting domain_id to scope it to a sending domain.
• Add the IP with POST /v2/email/ip_pools/{id}/ips.
• Track provisioning and warm-up state through the Dedicated IP API.