Amply
API integration

Ship Email features without building the integration. Full Amply API access via Proxy and 20+ MCP-ready tools for AI agents — extend models and mappings to fit your product.

Talk to us

Use Cases

Why integrate with Amply

Common scenarios for SaaS companies building Amply integrations for their customers.

Embed Amply as a BYO email provider

Notification platforms and CDPs can let their customers connect an Amply account, then route transactional sends through Amply's API on the customer's behalf without managing ESP-specific auth or payload quirks.

White-label sender domain onboarding

Multi-tenant SaaS products like storefront builders and CRMs can provision verified sender domains for each tenant, surface SPF/DKIM DNS records in their own UI, and trigger validation without exposing Amply as the underlying provider.

Build a deliverability command center

Analytics and auditing tools can pull IP addresses, IP pools, verified domains, and monitor state from a customer's Amply account into a unified dashboard for infrastructure health reporting.

Automated infrastructure alerting for tenants

Platforms that manage email for many customers can programmatically provision Amply monitors per tenant, so bounce spikes or reputation issues trigger webhooks back into the SaaS product.

Isolate transactional and marketing reputation

Platforms sending mixed traffic can dynamically create and assign IP pools per workload, protecting transactional deliverability from marketing-driven reputation swings.

What You Can Build

Ship these features with Truto + Amply

Concrete product features your team can ship faster by leveraging Truto’s Amply integration instead of building from scratch.

Transactional email dispatch

Send personalized emails through Amply with custom from/reply-to, recipient groups, attachments, and scheduled delivery via the create_a_amply_email endpoint.

Domain verification wizard

Programmatically create verified domains, fetch the exact DNS challenge records to display in your UI, and trigger remote validation once the user updates DNS.

IP pool manager

Let users create, update, and delete IP pools from inside your product to segment traffic by use case or tenant.

Dedicated IP inventory view

List and inspect dedicated IP addresses, flagging disabled IPs or missing rDNS configurations directly in your deliverability dashboard.

Monitor and alert provisioning

Create, update, and delete Amply monitors per tenant so bounce-rate or blocklist conditions fire webhooks into your platform automatically.

Multi-tenant infrastructure sync

Periodically pull IP pools, verified domains, and active monitors per connected Amply account to keep your internal state aligned with provider truth.

SuperAI

Amply AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

create_a_amply_email

Send an email via amply. Supply `from`, `personalizations` (with recipient `to` addresses), and either `content` or a `template` UUID to compose the message. Returns an empty JSON object on success.

list_all_amply_ip_addresses

List all IP addresses in amply. Returns an array of IP address objects including id, public_ip, enabled, status, rdns, and associated ip_pools.

get_single_amply_ip_address_by_id

Get a single amply IP address by id. Returns: id, public_ip, uuid, enabled, rdns, status, created_at, and ip_pools. Required: id.

update_a_amply_ip_address_by_id

Update an amply IP address by id. Returns the updated IP address object including id, public_ip, enabled, rdns, status, and ip_pools. Required: id.

delete_a_amply_ip_address_by_id

Delete an amply IP address by id. Returns an empty 200 response on success. Required: id.

list_all_amply_ip_pools

List all IP pools in amply. Returns an array of pool objects including id, name, uuid, status, and created_at.

get_single_amply_ip_pool_by_id

Get a single amply IP pool by id. Returns the pool object including id, name, uuid, status, created_at, and ip_addresses. Required: id.

create_a_amply_ip_pool

Create a new IP pool in amply. Returns the created pool object including id, name, uuid, status, and created_at.

update_a_amply_ip_pool_by_id

Update an existing amply IP pool by id. Returns the updated pool object including id, name, uuid, status, and created_at. Required: id.

delete_a_amply_ip_pool_by_id

Delete an amply IP pool by id. Returns an empty response on success. Required: id.

list_all_amply_monitors

List all monitors in amply. Returns an array of monitor objects including id, name, type, detection_method, detection_type, notifications, and alert_conditions.

get_single_amply_monitor_by_id

Get a single amply monitor by id. Returns the full monitor object including id, name, type, detection_method, detection_type, notifications, alert_conditions, and created_at. Required: id.

create_a_amply_monitor

Create a new monitor in amply. Returns the created monitor object including id, name, type, detection_method, detection_type, alert_conditions, and created_at.

update_a_amply_monitor_by_id

Update an existing amply monitor by id. Returns the updated monitor object including id, name, type, detection_method, alert_conditions, and created_at. Required: id.

delete_a_amply_monitor_by_id

Delete an amply monitor by id. Returns an empty response on success. Required: id.

list_all_amply_verified_domains

List all verified domains in amply. Returns an array of domain objects including id, name, deliverability_strategy, status, and created_at for each entry.

get_single_amply_verified_domain_by_id

Get the DNS challenge records for an amply verified domain by id. Returns: spf, dkim, whitelabel, and shared values representing the CNAME and TXT records that must be created to complete domain verification. Required: id.

create_a_amply_verified_domain

Create a verified domain in amply. Returns the created domain object including id, name, deliverability_strategy, status, and created_at. Required: name.

update_a_amply_verified_domain_by_id

Update a verified domain's deliverability strategy in amply by id. Returns the updated domain object including id, name, and status. Required: id.

delete_a_amply_verified_domain_by_id

Delete a verified domain in amply by id. Returns an empty response on success. Required: id.

get_single_amply_verified_domain_dns_challenge_by_id

Get the DNS challenge details for a verified domain in Amply. Required: verified_domain_id.

create_a_amply_verified_domain_validation

Trigger validation for a verified domain in amply. Initiates the validation process for the specified domain. Required: verified_domain_id.

Why Truto

Why use Truto’s MCP server for Amply

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 500+ integrations.

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

How It Works

From zero to integrated

Go live with Amply in under an hour. No boilerplate, no maintenance burden.

Link your customer’s Amply account

Use Truto’s frontend SDK to connect your customer’s Amply account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

Call our API, we call Amply

Truto’s Proxy API is a 1-to-1 mapping of the Amply API. You call us, we call Amply, and pass the response back in the same cycle.

Unified response format

Every response follows a single format across all integrations. We translate Amply’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about Amply on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

How does authentication to Amply work through Truto?

End users connect their Amply account by supplying an Amply API access token. Truto stores and rotates credentials, and your application calls Amply tools through Truto without handling the token directly.

Which Amply resources can I read and write today?

The integration supports sending email, full CRUD on IP pools, monitors, and verified domains, read/update/delete on dedicated IP addresses, and fetching DNS challenges plus triggering validation on verified domains.

Can I programmatically verify sender domains for my tenants?

Yes. You can create a verified domain, retrieve its DNS challenge records (SPF/DKIM/CNAME), display them in your UI, and call the validation endpoint once the tenant updates DNS.

Does the email send endpoint support templates, attachments, and scheduling?

Yes. The create_a_amply_email tool accepts raw HTML/text or Amply template UUIDs, supports To/CC/BCC, attachments, and the send_at parameter for scheduled delivery.

Can I receive real-time events like bounces or blocklist alerts?

Amply itself emits alerts via Monitors you configure through the create_a_amply_monitor tool. You provision monitors with the conditions you need and Amply delivers the resulting alerts to your configured destination.

Is there a unified Email API I can target instead of Amply-specific tools?

Not for this integration yet. You currently call Amply directly through Truto's typed tools, which means full fidelity to Amply's schema without abstraction loss.

Amply

Get Amply integrated into your app

Our team understands what it takes to make a Amply integration successful. A short, crisp 30 minute call with folks who understand the problem.