Skip to content

🔧 Technical Questions

Q: What programming languages do you support?

MailerLogic works with any language that can speak SMTP or HTTP/REST. We provide examples in cURL, Node.js, Python, and PHP, and you can use any standard HTTP or SMTP client in your stack (Go, Java, Ruby, .NET, etc.).

Q: Do you have SDKs or libraries?

Official SDKs are coming soon. Until then you can use:

  • Standard SMTP libraries (Nodemailer, PHPMailer, Python smtplib, etc.)
  • Any HTTP client (Axios, requests, fetch, Guzzle, etc.) to call the REST API

Q: What's your API rate limit?

We separate API request limits from email throughput and quotas.

API request rate limit

  • Default: 600 requests per minute per customer
  • Applies to all REST API endpoints
  • Enforced via HTTP 429 with standard rate-limit headers:
    X-RateLimit-Limit: 600
X-RateLimit-Remaining: 543
X-RateLimit-Reset: 1733686805

Email throughput limits

  • Shared IP pool: 50 emails/second (default)
  • Dedicated IPs: 500 emails/second (default, after warm-up)
  • Configurable per customer based on reputation and use case
  • When you exceed the throughput limit, emails are queued, not rejected. Our send engine drains the queue at the optimal rate for your account and IP reputation.

Daily & monthly quotas

  • Daily sending quota: 50,000 emails/day (default)
  • Monthly quota: 1,000,000 emails/month (default)
  • When you exceed a quota, new send requests are rejected with a quota_exceeded error until the limit resets or is increased.

Batch sending

  • Maximum 1,000 recipients per API call for /api/batch and /api/bulk-send
  • Encourages efficient use of the API and reduces overhead for high-volume senders

Why this design?

Many providers rely on strict per-request limits or return 429 for large send bursts. MailerLogic accepts your requests, queues emails internally, and sends at the correct rate for your configuration and reputation. This lets you run large campaigns reliably without manually managing backoff or throttling logic in your application.

If you need higher limits, contact support with your use case and we'll tune your configuration.

Q: Do you have a sandbox environment?

A dedicated sandbox environment is coming soon. In the meantime you can:

  • Send small volumes through production using test domains
  • Use the Content Scoring API to validate templates before real sends
  • Lock sending to internal/whitelisted recipient addresses during integration

Q: How do I test webhooks locally?

You can use any HTTP tunneling or webhook inspection service, for example:

  • ngrok – exposes localhost over HTTPS
  • webhook.site – simple endpoint that shows incoming payloads
  • RequestBin – captures and inspects webhook requests

Point your MailerLogic webhook URL at the generated public URL while you build and debug.

Q: Can I use MailerLogic behind a firewall?

Yes. Make sure your firewall allows:

  • Outbound HTTPS on port 443 for API calls
  • Outbound SMTP on ports 587 or 2525 for sending via SMTP
  • Inbound HTTPS on your webhook endpoint if you want to receive events

Q: What's your uptime SLA?

We target 99.9% uptime. Enterprise plans include:

  • Contractual SLA guarantees
  • Priority & on-call support
  • Incident notifications via our status page

Status page: https://status.mailerlogic.com