Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.spotzee.com/llms.txt

Use this file to discover all available pages before exploring further.

Spotzee doesn’t ship its own email transport. You bring an email provider, give Spotzee credentials, and we route your sends through it. Four providers are supported: SMTP, SendGrid, Mailgun, and Amazon SES.
Provider configuration lives under Settings → Integrations and requires the project admin role. You can add more than one provider; mark one as the default and use the others as fallbacks.

​
Pick a provider

Each provider takes a different credential shape:
ProviderBest forCredentials
SMTPBring-your-own relay or a vendor outside this listHost, port, protocol, username, password
SendGridHigh-volume marketing email with built-in deliverability toolingAPI key
MailgunTransactional and marketing email with strong analyticsAPI key, domain, optional webhook signing key
Amazon SESCost-sensitive senders running other infrastructure on AWSRegion, access key ID, secret access key
If you’re unsure, start with SMTP for an existing relay, or SendGrid if you’re starting fresh and want the simplest credential.

​
Configure your provider

Use SMTP when you have a third-party relay or an in-house mail server. Spotzee speaks any standard SMTP server.
1

Add a new email provider

In Settings → Integrations, add a new email provider and pick SMTP.
2

Enter connection details

Fill in the credentials your relay gave you:
  • Host. The SMTP server hostname.
  • Port. Typically 587 for STARTTLS, 465 for SSL, 25 for plain.
  • Protocol. Pick starttls (recommended), ssl, tls, or plain. STARTTLS is the modern default.
  • Username and Password.
  • Auth type (optional). Defaults to AUTO. Switch to LOGIN or PLAIN only if your server requires it.
  • Custom headers (optional). Add tracking headers your downstream analytics needs.
3

Save and test

Save the provider, then send a test message (see Test the connection below).

​
Test the connection

Each provider has a test-send affordance. Run one before you point real campaigns at the provider.
1

Open the provider you just saved

In Settings → Integrations, open the provider’s row.
2

Send a test email

Use the test-send action and supply a destination address you can read.
3

Check the result

A successful send confirms credentials, network access, and DNS auth (SPF/DKIM/DMARC) are healthy. A failure surfaces the underlying error message.

​
Set the default provider

Spotzee picks the default email provider for any send that doesn’t name one. Mark one provider as default after you save it. Add more providers as fallbacks; the routing layer prefers the default and only falls back when the default fails or is disabled. For sending domain configuration (DKIM records, link wrapping, deliverability hardening), use Settings → Domains.

​
Webhook callbacks

Spotzee uses provider-specific webhooks to receive delivery events (delivered, bounced, complained, opened, clicked). Each provider exposes its own callback URL in the setup metadata after you save the provider:
  • SendGrid: a single Webhook URL for the Event Webhook.
  • Mailgun: a Feedback URL for delivery events. Use the optional webhook signing key to verify inbound payloads.
  • Amazon SES: a Feedback URL for SNS-published events (bounces, complaints, deliveries).
SMTP doesn’t have webhook callbacks. Open and click tracking still works through Spotzee’s tracking domain regardless of provider.

​
Next steps

Provider catalogue

Compare providers across email, SMS, push, webhook, and in-app.

Manage API keys

Issue the keys your servers and apps use to talk to Spotzee.

Trigger a campaign

Send a one-shot campaign through the API.

Sync users

Push your user base into Spotzee with sk_ keys.