Migrate from Postmark
Motorical Sending SMTP is in the same job class as Postmark for transactional email (HTTP send + SMTP + delivery webhooks). This page is a thin mapping — not a feature-by-feature comparison. For product positioning see Compare.
A Motorical SMTP Motor Block is an isolated sending stream (similar to a per-app/per-tenant ESP project): its own domain, API keys, SMTP credentials, rates, logs, and webhooks.
Concept map
| Postmark-style concept | Motorical |
|---|---|
| Server / server token | Motor Block + Motor Block API key mk_live_... |
| Send email HTTP API | POST https://api.motorical.com/v1/send (Authorization: ApiKey or X-Api-Key) |
| SMTP | mail.motorical.com:2587 (STARTTLS) or :2465 (implicit TLS) |
| Message stream / isolation | Separate Motor Blocks for apps, tenants, or staging vs production |
| Webhooks | Public API webhooks; verify X-Motorical-Signature |
| Sandbox / test send | dryRun: true on POST /v1/send |
| Account API / stats | Mint bearer with ak_live_..., then /api/public/v1 |
Minimal send (HTTP)
- Create a Motor Block and verify your sender domain.
- Create a Motor Block API key (
mk_live_...). - Dry-run, then send for real (omit
dryRunor setfalseonly when ready):
curl -X POST "https://api.motorical.com/v1/send" \
-H "Authorization: ApiKey $MK_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": "noreply@yourdomain.com",
"to": ["you@example.com"],
"subject": "Migration dry-run",
"text": "Hello from Motorical",
"dryRun": true
}'
Do not use OAuth or Bearer tokens on POST /v1/send.