Frequently Asked Questions

EmailSendX works with any provider that supports SMTP authentication. The most common setup is Amazon SES (lowest cost at $0.10 per 1,000 emails). Other supported providers include Mailgun, SendGrid, Postmark, SMTP2GO, SparkPost, and any custom SMTP server. You connect your own provider credentials — EmailSendX routes your email through your account, so you own the sending relationship and costs.

EmailSendX pricing is based on the number of contacts in your workspace and the number of emails sent per month. Plans start from free (Hobby: 500 contacts, 1,000 emails/month). Paid plans scale based on contact and email volume. See the pricing page for current plan details. Note that email sending costs are separate — you pay your own provider (e.g., AWS SES) directly.

Yes. For sending: verify your domain (e.g., yourdomain.com) in Workspace Settings → Sending Domains. This allows you to send from @yourdomain.com addresses. For tracking: configure a custom subdomain (e.g., track.yourdomain.com) as a CNAME pointing to EmailSendX's tracking endpoint. Both are fully supported and recommended for best deliverability.

Yes. The Hobby plan is free with no credit card required. It includes 1 workspace, up to 500 contacts, 1,000 emails per month, and access to all core features — campaigns, automations, forms, and templates. You connect your own email provider (AWS SES, SMTP). The free plan does not include webhooks, advanced A/B testing, or the CRM add-on.

When you reach your contact or email send limit, EmailSendX pauses further sends and notifies you via email. Existing contacts and data are not deleted. You can upgrade your plan immediately to resume sending. We don't charge overages automatically — you're always in control.

Hard bounces (permanent delivery failures like invalid email addresses) automatically suppress the contact — they won't receive future emails. Soft bounces (temporary failures like full mailboxes) are logged but don't immediately suppress. After 3 consecutive soft bounces, a contact is auto-suppressed. Spam complaints are received via AWS SES feedback loops and also auto-suppress the contact. You can view all suppressed contacts in Contacts → filter by status.

EmailSendX supports white-labeling on the Business plan and above. White-label features include: custom domain for the app (app.yourbrand.com), custom logo and color scheme, removal of EmailSendX branding from emails and footers, and client-facing workspaces. Contact sales@emailsendx.com for white-label setup.

Yes, completely. Each workspace is a fully isolated environment. Contacts, campaigns, automations, API keys, and settings in one workspace are completely separate from any other workspace — even if they belong to the same account. An API key from workspace A cannot access data from workspace B. This makes EmailSendX safe for managing multiple clients or brands.

Yes. Double opt-in is available on all plans. When enabled, a confirmation email is sent to new subscribers before they're added as active contacts. Only subscribers who click the confirmation link are activated. Enable it in Workspace Settings → Signup Forms → Require double opt-in. Double opt-in is recommended for GDPR compliance as it creates a verified consent record with a timestamp.

Yes. EmailSendX has an official Zapier integration with triggers (New Contact, Email Bounced, Campaign Sent, Email Complained) and actions (Create/Update Contact, Add Contact to List). Search for "EmailSendX" in Zapier to find the app. REST Hooks (near-real-time events) are available on Zapier Pro and above. See the Zapier integration guide for setup instructions.

New AWS SES accounts start in sandbox mode, which limits sending to verified email addresses only. To send to real audiences: go to AWS Console → Simple Email Service → Account dashboard → Request production access. Fill out the form with your use case (marketing emails, transactional emails, estimated daily volume). AWS typically approves within 24–48 hours. Make sure your bounce rate will be low — a clean, opt-in list is important for approval.

The EmailSendX REST API allows 120 requests per minute per API key, using a sliding window algorithm. Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers so you can monitor your usage. When you exceed the limit, a 429 Too Many Requests response is returned with a Retry-After header indicating how many seconds to wait. See the Rate Limits guide for retry logic examples.

Yes, in two ways: 1) Enroll a contact in an automation using POST /automations/{id}/enroll — the automation sends emails according to its configured steps and delays. 2) Fire a custom event using POST /contacts/{id}/events — any active automation with a matching CUSTOM_EVENT trigger will run for that contact. Full campaign creation and sending via API is not currently supported — use the dashboard for campaign design and scheduling.

EmailSendX acts as a data processor and is built with GDPR requirements in mind. Features include: double opt-in with consent timestamps, one-click data export per contact, personal data deletion (right to erasure), suppression list management, and a Data Processing Agreement (DPA) available on request. Email legal@emailsendx.com to request a signed DPA. See the GDPR & Privacy guide for full details.

The API documentation lives at /docs/api — it covers authentication, contacts, lists, segments, campaigns, automations, events, and error codes with request/response examples. The machine-readable OpenAPI spec is available at /api/v1/openapi.json if you want to generate client SDKs or import it into Postman/Insomnia.