Getting Started and Authentication

Q: How does the MailChannels Email API work?
A: MailChannels Email API is a RESTful HTTP service for sending transactional emails. Your application sends an HTTP POST request with the email content (in JSON) to MailChannels, and our cloud service handles the actual email delivery (Link). This means you don’t need to run your own mail server – just integrate the API and let MailChannels ensure the message is delivered reliably.

Q: How do I sign up and start sending emails with MailChannels?
A: To get started, sign up on the MailChannels website. You’ll need a business email and a valid credit card on file for verification (Email API Documentation - Account Creation). After activating your account, log in to the MailChannels Console. There, you should create an API key (with “api” scope) and set up a Domain Lockdown record for each domain you’ll send from (Email API - Authentication Prerequisites). Once those are in place, you can immediately start sending emails via the API.

Q: What is an API key and how do I get mine?
A: An API key is a secret token used to authenticate your API calls. In the MailChannels Console, go to Settings > API Keys and click “Create API Key” to generate a new key with the api scope (Email API - Generate an API Key). You can give each key a descriptive name (for example, per application). MailChannels recommends using separate API keys for different apps or sites – that way you can revoke a single key without affecting others (Support - What is my API Key?). Keep your API keys safe, as they act like passwords for the API.

Q: How do I authenticate my API requests?
A: Every API request must include your API key in the HTTP headers. Specifically, set the X-Api-Key header to your API key value. No additional username/password is needed – the API key alone authenticates you. For example, in a cURL request you would include -H "X-Api-Key: YOUR-API-KEY" in the command. (Ensure the key has the proper scope “api” when you create it.) MailChannels may respond with 403 Forbidden if the API key is missing, invalid, or doesn’t have access to the feature you’re trying to use (Email API - Send an Email).

Q: Can I send email from any domain using MailChannels?
A: Yes, you can send on behalf of any domain you own – but you must first verify you control the domain. MailChannels uses a feature called Domain Lockdown to authorize your domains. You’ll add a TXT record in DNS (_mailchannels.yourdomain.com) containing your MailChannels account ID (Email API - Setting up Domain Lockdown). This proves to MailChannels that you own the domain and prevents others on the platform from impersonating your domain. Once the Domain Lockdown record is in place for “yourdomain.com,” you can send from addresses at that domain.

Q: Why do I need to create a Domain Lockdown record?
A: Domain Lockdown is a security measure unique to MailChannels. Without it, any MailChannels customer theoretically could try sending from your domain. The Domain Lockdown DNS record ties your domain to your MailChannels account, ensuring no one else can send pretending to be you. In short, it protects your domain from spoofing by unauthorized senders on the MailChannels platform. It’s a one-time DNS setup per domain.

Q: Do I need to update DNS records like SPF or DKIM for MailChannels?
A: It’s highly recommended. If you use SPF (Sender Policy Framework) for your domain, you should include MailChannels in your SPF record to authorize their mail servers. For example, add include:relay.mailchannels.net in your domain’s SPF TXT record. This helps recipient servers know MailChannels is allowed to send for your domain. As for DKIM, MailChannels supports it but doesn’t provide a default key — you can bring your own DKIM keys. You would publish a DKIM public key as a DNS record (for a selector on your domain), and in your API request provide the matching private key along with your domain and selector (Email API - Using DKIM). This lets MailChannels sign outgoing messages with DKIM on the fly. While not mandatory to send, setting up SPF and DKIM will improve your deliverability and are required by some inbox providers if you send large volumes. (MailChannels also adheres to DMARC policies when you have those in place.)