Fragmented integrations
One SDK for email, another for SMS, another for WhatsApp — each with its own errors, limits and payloads.
Notification API
One API for email, SMS and WhatsApp
Stop wiring up a different provider for every channel. Notify handles delivery, retries failures and tells you exactly what happened to each message.
In development · early access program open
Sending a notification shouldn't take three integrations
No retries, no fallback
When a provider fails, the message is gone unless you build your own queue and retry policy.
No visibility
Support asks whether the verification code arrived, and nobody can answer for sure.
How it works
Send a request with the channel, the recipient and the template. Notify does the rest.
Define your template once
With per-language variants. Recipients get the message in their language, with automatic fallback.
Call the API
You get a 202 in milliseconds: the message is queued and delivered in the background.
Check the real status
Accepted, sent, delivered or failed — with the full history of attempts per provider.
Send a payment reminder
curl https://api.notify.com.mx/v1/messages \
-H "Authorization: Bearer $NOTIFY_API_KEY" \
-H "Idempotency-Key: invoice-8812-reminder" \
-H "Content-Type: application/json" \
-d '{
"channel": "whatsapp",
"recipient": { "address": "+525512345678", "locale": "es" },
"template_key": "payment_reminder",
"variables": { "name": "Ana", "amount": "$1,250.00 MXN" }
}'Response
HTTP/1.1 202 Accepted
{
"id": "6f1c2a4e-9b7d-4c1e-8a35-2d0f5b9e7c11",
"status": "accepted",
"channel": "whatsapp",
"template_key": "payment_reminder",
"resolved_locale": "es",
"created_at": "2026-10-05T17:42:08Z"
}Channels
Transactional email from a verified domain, with bounce tracking.
SMS
E.164-normalized numbers and native STOP opt-out handling.
Meta-approved templates over the official WhatsApp Business API.
Production-ready from the very first message
Native multilingual templates
Language cascade: recipient → customer default → Spanish.
Idempotency
Retry safely: the same Idempotency-Key never sends twice.
Queued retries
Per-channel workers and a dead-letter queue, so nothing fails silently.
Queryable audit trail
Who sent what, to whom, and with what result — ready for support and compliance.
Opt-out enforcement
If a recipient unsubscribed from a channel, the message is blocked before it leaves.
Built for LATAM
Providers, channels and pricing designed for the Latin American market.
Be among the first teams on Notify
We're validating all three channels with real traffic. If your team sends transactional notifications, we'd love to talk.
Get in touch