Authenticated from the first send
Your domain carries the DKIM CNAME before you go live, and PUT /domain/dns/check confirms DKIM and SPF. Transactional email deliverability.
Onboarding
How tinyRelay onboarding works.
tinyRelay onboarding is done with our team, in four steps. You tell us what you send, share a webhook URL and the IPs you call from, set up your sender domains with one DKIM record, and we send your API key and SMTP credentials.
ONBOARDING · 4 STEPSno fixed turnaround
YOUillustrative
Tell us about your sending
What you sendPassword resets · Receipts · Alerts
Roughly how muchA monthly range
How you sendSMTP · REST API · Both
YOUillustrative
Share your webhook URL and calling IPs
Webhook URL · accepts POSThttps://yourapp.com/webhooks/tinyrelayPublic
Calling IPs203.0.113.10 · 203.0.113.11Allowlisted
YOU + USillustrative
Set up your sender domains
Senders you shareno-reply@yourdomain.comAdded by us
DKIM CNAME you addtec1._domainkey → tec1.dkim.tinyemail.comYour DNS
US, THEN YOUillustrative
Receive your credentials and send
API key
In a header
SMTP
Credentials
Webhooks
Signing secret
- 202requestId returnedfirst send
- SENDat your webhooksigned ✓
- DELIVEREDat your webhooksigned ✓
The four steps
From the form to your first send.
Two steps are yours, one we do together, and the last one starts with us. Each step is in the setup section of the docs.
- 1YOUTell us about your sending
Submit the Get started form with what you send, roughly how much, and whether you will use SMTP, the REST API or both.
- 2YOUShare your webhook URL and calling IPs
Give us a public URL that accepts POST requests for webhook events, and the IP addresses you will call the API from so we can allowlist them.
- 3YOU + USSet up your sender domains
Share the senders you will use so we can add their domains to our mail servers, and add the DKIM CNAME record tec1._domainkey to each domain.
- 4US, THEN YOUReceive your credentials and send
We send your API key, SMTP credentials and webhook signing secret. Your first API request returns 202 with a requestId, and events start arriving at your webhook.
No fixed turnaround is published; timing depends on your DNS changes and details.
Why a person sets you up
Setup protects your deliverability. And everyone else's.
tinyRelay accounts are set up with our team rather than through a self-serve sign-up, because the first send matters: mail from an unauthenticated domain, or from a sender nobody expected, is exactly what receiving servers learn to distrust.
tinyRelay runs on the same email delivery infrastructure as tinyEmail, looked after by the same team. Setting up domains and senders properly before you send keeps that infrastructure, and your own domain's reputation, in good shape.
Known senders only
We add the domains of the senders you share with us to our mail servers. Your From addresses are the ones you planned.
Calls locked to your network
Your calling IPs are allowlisted and your key travels in a header. How tinyRelay handles security.
What to have ready
Five things that make setup quick.
Gather these before you fill in the form. Tap each one as you get it ready.
All five come from the setup section of the tinyRelay docs.
Tap the ones you already have.
Public webhook URLYour own public API endpoint that accepts POST requests. Every webhook event is sent there.Calling IP addressesThe list of IPs you will call the API from. We allowlist them for security.Sender addressesThe From addresses you will send as. We add their domains to our mail servers.DNS accessSomeone who can add a CNAME: host tec1._domainkey.yourdomain.com, value tec1.dkim.tinyemail.com.SMTP, API or bothHow your app will send. Existing mailers suit the SMTP relay; new code suits the email API.
Not sure which way to send?
Existing mailers suit the SMTP relay; new code suits the email API. You can use both.
I have these, get startedAfter setup
What you get back.
Four things to store and one address to note. Then send your first message.
API KEY
X-RELAY-ACCESS-TOKEN
Sent in a header on every API call. Keep it server-side.
SMTP CREDENTIALS
Username + password
For your framework mailer or any SMTP client. Connection details are confirmed at onboarding.
SIGNING SECRET
One per endpoint
Used to verify svix-signature on every webhook request.
WEBHOOK SOURCE IP
3.229.12.181
Allow it through your firewall if inbound traffic is restricted.
Before you go live
Three checks for your first day.
Credentials in hand, run these before real users depend on your email. Each one uses something documented, so you know exactly what a pass looks like.
Validate your domain
Call PUT /domain/dns/check with your sending domain. DKIM and SPF should both come back Valid. If one says Invalid, the response lists the record it expected to find.
Send to yourself
Send one message to an address you control, with a test value in metadata. The API should answer 202 with a requestId. A 401 means the key or header is wrong; check the calling IP is the one you gave us.
Watch the events arrive
SEND and then DELIVERED should reach your webhook URL with your test metadata attached. Verify the svix-signature on each one before you trust it, exactly as you will in production.
Sending over SMTP instead? Point your mailer at the relay with the credentials we issued, send the same test message, and confirm it arrives signed for your domain. Laravel, Django and Rails guides show where each setting goes.
FAQ
Onboarding questions.
What people ask before they fill in the form.
How long does tinyRelay onboarding take?
It depends mostly on how quickly your DNS changes and details come together. We do not publish a fixed turnaround. Tell us your timeline on the form and our team will tell you what to expect.
Is there a self-serve sign-up or free trial?
Setup goes through our team today, starting with the Get started form. If you need a way to test before you go live, ask us.
What do I need before I start?
A public webhook URL that accepts POST requests, the IP addresses you will call the API from, the sender addresses and domains you will use, access to add a DNS CNAME record, and a choice of SMTP, the REST API or both.
What if my server IP addresses change?
Send the new addresses to our team before you switch. API calls are accepted from allowlisted IP addresses, so update the list first.
Do I need to allowlist tinyRelay's IP address?
If your firewall restricts inbound traffic, allow 3.229.12.181, the address webhooks are sent from. Verify each request's signature as well.
Get started
Send transactional email with a service that reports back.
SMTP relay or REST API, standalone or alongside tinyEmail. Tell us what you send and our team sets you up.