ProductPricingCompareCheck your domainDocsDashboardSign inGet started
Docs / REST API

Start

  • Overview
  • Getting started
  • Connect a mailbox

Sending

  • Domains
  • Mailboxes
  • Sending safety

Leads and campaigns

  • Leads
  • Campaigns
  • Write with AI

Replies and results

  • Unibox and AI labels
  • Analytics

Workspace

  • Team and roles
  • Billing and plans
  • Integrations

Developers

  • Connect your AI (MCP)
  • REST API
    • Overview
    • Workspace5
    • Analytics1
    • Campaigns26
    • Leads16
    • Lists4
    • Labels6
    • Suppressions3
    • Unibox6
    • Mailboxes8
    • Warmup3
    • Deliverability Network4
    • Domains4
    • Link domain5
    • Integrations3
    • Webhook endpoints7
    • Offer profile3
    • Billing1
    • Domain checker1
    • API keys1
  • Webhooks

Start

  • Overview
  • Getting started
  • Connect a mailbox

Sending

  • Domains
  • Mailboxes
  • Sending safety

Leads and campaigns

  • Leads
  • Campaigns
  • Write with AI

Replies and results

  • Unibox and AI labels
  • Analytics

Workspace

  • Team and roles
  • Billing and plans
  • Integrations

Developers

  • Connect your AI (MCP)
  • REST API
    • Overview
    • Workspace5
    • Analytics1
    • Campaigns26
    • Leads16
    • Lists4
    • Labels6
    • Suppressions3
    • Unibox6
    • Mailboxes8
    • Warmup3
    • Deliverability Network4
    • Domains4
    • Link domain5
    • Integrations3
    • Webhook endpoints7
    • Offer profile3
    • Billing1
    • Domain checker1
    • API keys1
  • Webhooks

Cold email that keeps your domains steady, with every feature on every plan.

Product

  • Features
  • Pricing
  • Sequences
  • Warmup
  • How it works
  • Docs
  • Changelog
  • Blog

Compare

  • Ballast vs Instantly
  • Ballast vs Smartlead
  • Ballast vs Lemlist
  • Switch from Instantly
  • Switch from Smartlead
  • Switch from Lemlist

Free tools

  • Domain checker
  • MX lookup
  • SPF checker
  • DKIM checker
  • DMARC checker
  • Blacklist check

Legal

  • Terms of Service
  • Privacy Policy
  • Acceptable Use Policy
  • Data Processing Agreement
  • Sub-processors

Developers

  • REST API
  • MCP server
  • OpenAPI spec
© 2026 BallastTermsPrivacy
All systems normal
ProductPricingCompareCheck your domainDocsBlogChangelogSign in

API reference

Deliverability Network

The IPs your SMTP and IMAP mailboxes log in through. 4 endpoints, each also a tool for your AI through MCP. Authentication and errors are on the overview.

Where your mailboxes connect from

GET/api/v1/sending-ip

SMTP/IMAP mailboxes connect through the Deliverability Network: the shared network on every plan, dedicated IPs, or your own proxy (API and MCP only). Microsoft and Gmail API mailboxes need none.

MCP tool get_sending_ipRead-only

Returns

requiredrequiredboolean
False only in development: mailboxes may then connect directly
ownrequiredobject | null
proxiesrequiredobject[]
waitingrequirednumber
Mailboxes waiting for a sending IP
directrequirednumber
Microsoft and Gmail API mailboxes, which need no proxy
dedicatedrequiredobject
cURL
curl https://ballast.to/api/v1/sending-ip \
  -H "Authorization: Bearer $BALLAST_API_KEY"

Test your own proxy without saving

POST/api/v1/sending-ip/own/test

Logs one of your SMTP/IMAP mailboxes in through it (or checks Gmail answers through it when you have none) and reads its IP type from IPinfo.

MCP tool test_own_proxyOwners and admins

Parameters

urlrequiredstring
socks5://user:pass@host:port or http://user:pass@host:port

Returns

okrequiredboolean
errorrequiredstring | null
exitIprequiredstring | null
countryrequiredstring | null
ipTyperequiredstring | null
IPinfo network type: isp is what you want; hosting means a datacenter
loginrequiredobject | null
SMTP AUTH and IMAP LOGIN of one of your mailboxes through the proxy
handshakerequiredobject | null
Gmail's SMTP 587 and IMAP 993 answering through the proxy
cURL
curl -X POST https://ballast.to/api/v1/sending-ip/own/test \
  -H "Authorization: Bearer $BALLAST_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"<url>"}'

Use your own proxy

PUT/api/v1/sending-ip/own

Tested first; saved only when it passes. Every SMTP/IMAP mailbox of the workspace then connects through it instead of the pool. Free on every plan.

MCP tool set_own_proxyOwners and admins

Parameters

urlrequiredstring

Returns

savedrequiredboolean
testrequiredobject
cURL
curl -X PUT https://ballast.to/api/v1/sending-ip/own \
  -H "Authorization: Bearer $BALLAST_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"<url>"}'

Stop using your own proxy

DELETE/api/v1/sending-ip/own

Your SMTP/IMAP mailboxes go back to the shared pool (they wait if it has no room).

MCP tool remove_own_proxyOwners and admins

Returns

okrequiredtrue
waitingrequirednumber
cURL
curl -X DELETE https://ballast.to/api/v1/sending-ip/own \
  -H "Authorization: Bearer $BALLAST_API_KEY"
PreviousWarmupNextDomains