What is the Mailbot transactional email API?

Mailbot ID is a transactional email API. Any backend, app, script, or automation sends one email by making an HTTPS POST request to https://api.mailbot.id/v1/send with a Bearer API key and a JSON body containing to, subject, and text or html.

How do I integrate Mailbot with my stack?

Mailbot uses plain HTTPS and JSON. Any language or platform that can send an HTTPS request with an Authorization header and a JSON body can integrate it — Node.js, Python, PHP/Laravel, Go, Ruby, serverless functions, and no-code automation tools all use the same POST /v1/send endpoint.

What can I send with Mailbot?

Transactional email triggered by your application: OTP codes, email and account verification, password reset links, invoice and receipt emails, order notifications, and system alerts. It is not for sending newsletters or bulk marketing.

Mailbot ID documentation

Mailbot transactional email API

Create an account, verify your sender domain, then send transactional email from any backend, app, script, or automation over one HTTPS API.

Buat akun gratis Lihat integration guide

Answer first: Mailbot is a transactional email API. Start by creating an account, verify the sender domain, then make an authenticated HTTPS POST to https://api.mailbot.id/v1/send with your Mailbot API key and the email payload.

Anything that can make an HTTPS request can integrate it — Node.js, Python, PHP/Laravel, Go, Ruby, serverless functions, and no-code automation tools. Self-serve accounts start with 1,000 emails/month and Rupiah top-up after sender verification.

cURL

curl https://api.mailbot.id/v1/send \
  -H "Authorization: Bearer mb_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "user@example.com",
    "subject": "Your verification code",
    "text": "Your code is 884921"
  }'

Start here

Integration

Integration guide

Stack-agnostic HTTPS API model: base URL, authentication, JSON request/response contract, errors, idempotency, and copy-paste examples for cURL, Node.js, Python, and PHP/Laravel.

Reference

API reference

Every endpoint: POST /v1/send, GET /v1/status, POST /v1/test-email, plus account and top-up endpoints. Methods, auth, fields, and responses.

Transactional email use cases

Each guide ties one product event to a concrete API call, required fields, an example payload, the example response, errors, testing, and a production checklist.

OTP email API

Send one-time passcodes for login, transaction confirmation, and step-up auth.

Email verification API

Confirm a new user owns their email address with a verification link or code.

Reset password email

Deliver secure, expiring password reset links on demand.

Invoice & receipt email

Send payment receipts and invoices automatically after a transaction.

Order notification email

Notify customers of order confirmation, shipping, and status changes.

System alert email

Page operators and users when your backend detects an event or failure.

What Mailbot is — and is not

Is: a transactional email API for application-triggered messages, with docs and examples for developer workflows.
Is not: a newsletter sending or bulk-marketing tool, an inbox, a helpdesk, or an email client. Mailbot does not receive email.
Pricing: 1,000 emails/month free forever, top-up kredit from Rp 30rb, and higher-volume packages when you need more capacity. See pricing.

Current availability

Start from account creation: create an account, submit your domain/sender, complete verification, then use the HTTPS API with 1,000 free emails/month. Top-up starts from Rp30rb after onboarding, and credits are added after payment succeeds.