Send receipts, password resets and alerts over a clean REST API or SMTP relay — on the same authenticated, warmed infrastructure as your marketing. One platform for every email your product sends.
POST to /api/v2/transactional/send with a to, a subject and an HTML body — that is the whole integration. Batch hundreds of messages in a single /batch call, and look up delivery status by ID whenever you need it.
curl, JavaScript, Python, Go, Java, Ruby & PHP examplesPoint your app or framework at Bluey's SMTP endpoint with a generated credential and start sending — no library, no rewrite. Same authentication, same delivery logs.
Delivery, opens, bounces and complaints for every transactional send land in the same dashboard as your campaigns. Look up any message by ID, or wire webhooks for real-time events.
Three steps from sign-up to send. Nothing in here costs extra, nothing requires a sales call.
Create a key in settings and pass it in the X-API-Key header. A test mode and a sandbox are there before you touch real traffic.
Call /transactional/send (or /batch for many), or point your SMTP client at our relay with a generated credential. Copy-paste examples in seven languages.
Check status by email ID, watch delivery and bounces in the dashboard, and subscribe webhooks so your app hears about every event in real time.
We moved password resets and receipts onto Bluey's API in an afternoon — and finally see product email and marketing in one place.
A separate transactional provider for product email and a different tool for marketing — two bills, two reputations, two dashboards.
Product and marketing email on one authenticated platform: one bill, one place to look.
Days wiring an SDK, templating and webhook plumbing before the first email leaves.
One authenticated POST — or SMTP — sends your first message in minutes.
Transactional mail on a cold, unknown IP that drops resets into spam.
The same warmed, SPF/DKIM/DMARC-authenticated sending as your campaigns.
Both. Use the REST API (/api/v2/transactional/send and /batch) or generate SMTP credentials and point any app or framework at our relay — same authentication and the same delivery logs either way.
Ready-to-paste snippets for curl, JavaScript, Python, Go, Java, Ruby and PHP. Authentication is a single X-API-Key header, so any HTTP client works.
Yes — there is a test mode and a sandbox so you can simulate sends and inspect payloads before switching to live traffic.
It runs on the same authenticated domains and warmed infrastructure, so your resets and receipts get the same inbox placement — and everything is visible in one dashboard.
Sign up, send a campaign, see what changes. No card, cancel anytime.