1
Add your domain
Go to Settings > Email Service > Email domains and click Add email domain. Enter the subdomain you want to send from, such as
mail.acme.com.Hiveku lists the DNS records to add at your DNS provider: three DKIM records, which are required, and the bounce-domain, SPF and DMARC records, which are recommended. Add them, then click Check Status. It usually takes a few minutes. See Email Domains for what each record does.2
Create a test key
Go to Settings > API Keys and click Create API Key. Name it, for example
dev-local, choose Test, and keep Send Emails selected.A test key (hk_test_...) runs every check and records the email, but delivers nothing. That makes it safe while you wire things up.3
Send your first email
Once the domain shows Verified, send from an address on it:With a test key, the answer says the email was simulated:
- curl
- Node.js
4
Check the logs
Go to Settings > Email Service > Email Logs and open the email you just sent. A test key’s email shows as Simulated, and opening it shows the whole message, so you can check that it rendered correctly. Opening an email’s content needs the Open sent emails permission, which owners and admins have. Hiveku keeps the message itself (its text and HTML) for 30 days after you send, then removes it; who it went to, the subject, the status, and the opens, clicks and bounces stay in the log.
5
Go live
Create a Production key (
hk_live_...) the same way and put it in your production environment. The same request then delivers the email, and answers "status": "sent".What’s next
- Send over SMTP from a framework or service that speaks SMTP.
- Set up Webhooks to track deliveries, bounces and opens.
- Moving an app? See Migrate from Resend or Migrate from Mailgun.
- Read Sending Emails for batches, templates, attachments and errors.
- Review Deliverability before your first large send.