Developers and AI assistants

Build on Mailsoftly. REST API, webhooks, MCP, and one-click connectors.

Everything in Mailsoftly is reachable from code and from AI assistants: contacts, lists, tags, segments, forms, templates, campaigns and their results, automations, landing pages and the account itself. One documented REST API powers all of it, and the same API drives the hosted MCP server that Claude and other assistants connect to. Sending is a separate permission everywhere, and the account's plan and trust level apply exactly as in the product.
Free to start · API keys in your account settings · OAuth for connectors
REST API v3Keys or OAuth, JSON in and out
WebhooksIn: start automations. Out: post contact data
MCP serverClaude directory, any MCP client
Your accountSame plan, same permissions, same guardrails
The reference at app.mailsoftly.com/developers is generated from the live API, so what it lists is what runs.
Join thousands of businesses
5.0
TrustRadius
4.8
4.9
5.0
5.0
Four doors, one platform

Pick the integration style that fits your team

Developers, no-code teams and AI assistants each get a first-class path. All of them end in the same account, under the same rules.
🛠️ REST API

Documented, versioned, scoped

Create and update contacts, manage lists, tags and segments, draft and send campaigns, read results, build automations. Every endpoint carries the permission it needs, so a key or an OAuth token can be as narrow as you like. API and webhooks page.

⚡ Webhooks

Events in, data out

Any app can start a Mailsoftly automation by posting JSON to a webhook endpoint you create, and any automation can post a contact's data to your system with a webhook step. No connector required.

🤖 MCP server

Every assistant, one server

The hosted MCP server exposes the product as curated tools with OAuth sign-in and a separate sending permission. Claude connects in one click from the directory; other clients add the server URL. MCP server page, Claude page.

🔗 Native connectors and Zapier

No code at all

Google Workspace, Microsoft 365, HubSpot, WordPress, Shopify and Jotform connect from the Integrations screen, and Zapier bridges thousands more. See the integrations overview.

Guardrails

The same rules as the product, explained in the response

An API call or an assistant never gets more than the account has. Plan limits are the published ones from the pricing page, sending needs a channel the account owns and a separate permission, and the first campaigns of every account pass a short content review. When something is held, the response says why and lists the steps that unlock it, so nobody has to guess.
Permissionscoped keys and tokens
Accountverified sending channel
Planpublished limits apply
Your call to sendseparate permission
FAQ

Building on Mailsoftly, answered

Where is the API documentation?

At app.mailsoftly.com/developers, next to your account. It is generated from the live API, includes an OpenAPI specification you can import into any client, and covers authentication, every endpoint and the permissions each one needs.

How do I authenticate?

With an API key from your account settings for your own integrations, or with OAuth for apps and assistants that act on behalf of your users. Both carry scopes, so a credential can read contacts without being able to send anything.

Can an AI assistant use the API?

Yes, through the hosted MCP server, which publishes the API as curated tools. Claude connects from the Claude directory in one click; any MCP client can add the server by URL. Sending is a separate permission the user grants on purpose.

Do plan limits apply to the API?

Yes, the same published limits as on the pricing page: contacts and emails per month for the plan, with any exception agreed for the account. Free accounts that have not verified a sending channel keep a small number of automations, forms and landing pages, and the API says so with the upgrade or verify path.

Is there a sandbox?

Every free account is one: you can create contacts, lists, drafts and automations and read everything back. Sending needs a sending channel the account owns, which is the same rule the product applies.

What can I do without writing code?

Connect Google Workspace, Microsoft 365, HubSpot, WordPress, Shopify or Jotform from the Integrations screen, bridge anything else through Zapier, or let an assistant do the work through the MCP server.

Start building today

Sign up free, create an API key in your settings, and make your first call in minutes.

Open the API reference Start free with Google Start free with Microsoft 365
No credit card required · Cancel anytime · Real humans on support