Transactional & product email, by API

Send email from
your code, not a
console.

mailme.co.in is an email sending API built for registered developers — a single endpoint for transactional mail, receipts, and notifications. It has run continuously since 2015, and remains fully available to every existing registered account.

Request access — closed Already registered? Contact us →

Stamped the moment registrations closed. Existing accounts keep sending — nothing changes for you.

send.sh — registered account
$ curl https://api.mailme.co.in/v1/send \
  -H "Authorization: Bearer <your_api_key>" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "user@example.com",
    "template": "receipt-v2",
    "data": { "amount": "₹1,299" }
  }'

// response
{ "status": "queued", "id": "msg_8f21ac" }
202 accepted · delivering
Service history
2015 mailme.co.in launches as a lightweight email sending API.
2018 Template engine and delivery webhooks added for registered accounts.
2022 Dedicated sending infrastructure for high-volume registered users.
07 Jul 2026 New registrations close. Existing accounts continue without interruption.
For registered users

Everything your account already has access to.

Since registrations are closed to new users, this is a reminder of what your existing account continues to run on.

01 · ENDPOINT

One API, every message

A single /v1/send endpoint for transactional mail, receipts, alerts, and digests — no separate products to wire up.

02 · DELIVERY

Delivery you can see

Every send returns a message id and status. Webhooks report queued, delivered, bounced, and opened events as they happen.

03 · ACCOUNT

Nothing changes for you

The registration close only affects new sign-ups. Your keys, quota, and templates keep working exactly as they do today.

Contact us

Questions about an existing account

This form is for registered users of mailme.co.in — billing, API limits, delivery issues, or anything else about your account. We don't process new registration requests.

Every message is verified with a one-time CSRF token and stored securely for our support team before it's ever visible to anyone else.