Introduction
Jumploon sends your application's email: receipts, password resets and alerts, plus newsletters and lifecycle campaigns. You talk to it through a REST API or SMTP, and it handles DKIM signing, retries, bounces, unsubscribes and event tracking.
Jumploon has two APIs:
- The REST API at
https://api.jumploon.com/emails,/domains,/contactsand so on. Start here. - The v3 API at
https://api.jumploon.com/v3/..., with Mail Send for per-recipient personalizations, plus templates, suppressions, stats and team management.
Both APIs share one account: the same domains, keys, templates, suppressions and message history. Use whichever fits your code, or both.
Before you start
You need:
- A Jumploon account. Log in at app.jumploon.com.
- A domain you control, so you can add DNS records. You'll send from an address on it, such as
hello@acme.com. - An API key, which you create in the dashboard.
Quickstart
Send your first email
Node.js, Python and cURL in five minutes.
Verify a domain
Publish DKIM, SPF and DMARC records.
Send over SMTP
From any app or device that speaks SMTP.
Receive events
Signed webhooks for deliveries, opens and bounces.
What you can do
| Area | What it covers |
|---|---|
| Sending email | Single, batch and scheduled sends, attachments, tags, idempotency |
| Templates | Handlebars templates with versions and a visual designer |
| SMTP | Send from any app or device that speaks SMTP |
| Contacts and Broadcasts | Store contacts, group them into segments, send newsletters |
| Automations | Multi-step sequences triggered by sign-ups or your own events |
| Inbound email | Receive mail on your domain and read it through the API |
| Webhooks | Signed delivery, open, click and bounce events |
| Activity, logs & stats | Per-message history, API request logs, daily statistics |
Where your data lives
Jumploon runs on its own servers in Falkenstein, Germany. Message history, contacts and templates are stored there. Outgoing mail is handed to our delivery network for the last hop to each recipient.