Hey DEV community! 👋 I'm the creator of MailBlinker, a temporary email service designed specifically for developers and automation enthusiasts. If you've ever struggled with parsing emails for OTP codes or confirmation links in your bots (like for embassy bookings or app sign-ups), you know how time-consuming it can be. Extra fluff text, delays, or unreliable inboxes can break your workflow.
In this post, I'll walk you through why I built MailBlinker, how its API works for seamless integration, and a step-by-step code example to get you started. Whether you're building side projects, testing APIs, or automating tedious tasks, this tool might just save you hours. Let's dive in!
The Problem: Email Verification in Automation
Picture this: You're coding a bot to grab free slots at embassies (a real pain point for me as a solo dev). The site sends a verification code to your email, but:
Standard temp email services dump the full message, forcing you to parse HTML or text for the OTP.
Delays in email delivery can timeout your bot.
No custom domains mean your emails look suspicious, triggering spam filters.
I faced this constantly, so I built MailBlinker to focus on instant, clean extraction. Our API doesn't just forward emails – it parses and delivers only the OTP or link you need, right away.
What Makes MailBlinker Different?
Free Tier: Instant disposable emails (e.g., ms3cgwumw0@mloqq.com) for privacy and quick tests. No sign-up required.
Premium Tier ($10/month): Custom usernames/domains (e.g., yourbot@xomll.com), folders for organizing inboxes, permanent mailboxes, and unlimited API access. Perfect for production bots or teams.
Powerful API: One endpoint to create inboxes, poll for messages, and extract OTPs/links automatically. Supports JSON responses for easy integration.
Use Cases:
Bot automation (e.g., scraping or booking systems).
API testing (simulate user sign-ups without real emails).
Privacy-focused apps (avoid sharing personal emails).
We've already got users loving it for its simplicity – check our blog for more stories, like "Why Developers Choose MailBlinker for OTP Handling."
Step-by-Step: Integrating MailBlinker API in Your Bot
Let's get hands-on! I'll use Node.js here, but it's language-agnostic (we have docs for Python, PHP, etc.).
1. Sign Up and Get Your API Key
Go to MailBlinker.com and create a free account.
Upgrade to Premium for API access ($10/mo – includes custom features).
Grab your API key from the dashboard.
2. Create a Temporary Inbox
Use the API to generate an email address on the fly.
fetch('https://mailblinker.com/api/mail/create-mail', {
method: 'POST',
headers: {
'Authorization': 'Bearer 5720c4dbb4601183486a9259a8e8f7b9b6fef2dc61f34ee901516995710e49aa',
'Content-Type': 'application/json'
},
body: JSON.stringify({ local_part: 'desired_username' })
})
.then(response => response.json())
.then(data => console.log(data))
.catch(error => console.error('Error:', error));
3. Poll for Messages and Extract OTP
Once your bot submits the email (e.g., to an embassy site), poll the inbox.
fetch('https://mailblinker.com/api/mail/last-unread-otp-or-link', {
method: 'POST',
headers: {
'Authorization': 'Bearer 5720c4dbb4601183486a9259a8e8f7b9b6fef2dc61f34ee901516995710e49aa',
'Content-Type': 'application/json'
},
body: JSON.stringify({ email: 'ms3cgwumw0@mloqq.com' })
})
.then(response => response.json())
.then(data => console.log(data))
.catch(error => console.error('Error:', error));
{
"otp": "123456",
"confirmation_link": "https://example.com/verify?token=abc123"
}
This extracts just the code (e.g., "123456") or link, skipping the rest. No regex nightmares!
Try It Out!
Head to MailBlinker.com and test the free tier. For premium, it's just $10/mo – no contracts. Got questions? Drop a comment below or DM me on X (@mailblinker).
What's your biggest pain with email automation? Share your stories – let's discuss! 🚀
Back to Blog
