Mailpro’s API lets developers send transactional and marketing emails directly from their software, without going through the web interface. Access requires login credentials and an API key, and every API call must follow our API Use Policy — an integral part of our Terms.

Quick rule: all communication is over SSL (HTTPS). Keep your API key secret — it is the equivalent of your account password for machine-to-machine traffic.

How API access works

  • Credentials: your Mailpro account credentials plus an API key issued by support
  • Endpoint: documented REST endpoints, all under HTTPS
  • Authentication: API key in the request header — never in the URL or in shared logs
  • Rate limits: we monitor usage to keep service quality stable for all customers

Acceptable use rules — same as the rest of Mailpro

API traffic is bound by the same acceptable-use rules as the web interface. You may not use the API to send spam, route purchased lists, target unauthorized industries, or attempt to bypass our content filters. We reserve the right to monitor API calls to verify compliance.

Confidentiality and privacy

If you share end-user data through our API, you must protect that data and publish a privacy policy in your integration that clearly explains what is collected, how it is used, and for what purpose. Our own commitments are in our data security page and the broader privacy policy.

Rate limits, fair use, and dedicated API

To preserve service quality for everyone, we may restrict or block clients whose API calls overload our servers. If you have specific volume requirements not supported by the standard API, contact support — we can offer a dedicated API plan tailored to your traffic.

Credits and reliability

API calls consume the same credits as web sends. Pair API integrations with automatic top-up so high-volume traffic never stops for lack of credits, and check the payment-declined guide for handling card failures. Subscription credits roll over while the subscription is active.

Updates and breaking changes

We reserve the right to modify or update the API and this policy at any time. Changes are communicated by email and on our website, and may impact how your integration behaves. Subscribe to our developer notifications to stay current.

Disclaimer

API integration is at your own risk, in accordance with our API documentation. Using the API does not constitute or imply a partnership or joint-venture relationship with Mailpro. For technical questions, contact our support team. To choose between API and SMTP for your use case, read the differences between SMTP and API.

Get your API key

Contact our technical support with your Mailpro account email to request your API key. Read the SMTP guide if you prefer SMTP, or stick with the API for tighter app integration.

Previous question

   

Next question

You might also be interested in:

Are Email Addresses Case Sensitive?

Short answer: in everyday email use, addresses are treated as case-insensitive. Sending to [email protected] or [email protected] reaches the same inbox...

Read more

What Are the Differences Between Texting and Email?

Texting and email both deliver written messages, but they target very different moments. SMS goes straight to the phone in...

Read more

What Does Emailing Mean?

Emailing refers to the practice of sending email at scale — usually to a list of contacts — for marketing,...

Read more

Do I need my own domain name to do email marketing?

Strictly speaking, no — you can technically send a Mailpro campaign from a free Gmail or Outlook address. In practice,...

Read more

What Is a Password Reset Email?

A password reset email is the automated message a service sends when a user clicks « forgot password ». It...

Read more

Unleash the Power of Professional Email Marketing

Secure, scalable, and built for impact. Join Mailpro™ today and enjoy 500 free credits to send your first campaign.
Start Sending for Free