India’s software industry builds products for customers at home and around the world. Whether you run a fintech app in Bengaluru, an e-commerce platform in Gurugram or a SaaS product in Pune with clients in Europe, your application needs to send email reliably: login codes, invoices, receipts, alerts and onboarding messages. Mailpro’s email API lets you do that from your own code while keeping one dashboard for statistics and contacts.
What you can do with the API
- Send emails from your application: trigger transactional messages (password resets, order confirmations, GST invoices) or campaign emails using content generated by your system.
- Retrieve statistics: download opens and clicks, including by country, to feed your own dashboards. See email API statistics.
- Manage contacts and lists: add, update and segment contacts automatically based on what users do in your product.
- Receive webhooks: get delivery, bounce and engagement events pushed to your endpoint; see the three types of Mailpro webhooks.
Typical Indian use cases
Fintech and banking
Transaction alerts, statements and KYC reminders need to arrive quickly and be clearly separate from marketing. Keeping them on the API, with their own templates and sender address, protects their deliverability. Banks and NBFCs should also check sector rules from their regulator on data storage and outsourcing before choosing any provider.
E-commerce and D2C
Order, dispatch and delivery emails are the messages customers read most closely. Send them through the API from your store platform, and use the same contact data for consent-based marketing.
SaaS and IT services
Product teams use the API for sign-up verification, trial reminders and usage reports, often to customers across several time zones. Scheduling is simpler when your sending logic lives in your own code.
Edtech
Class reminders, assignment notices and results emails can be triggered directly from your learning platform.
API or SMTP?
If your application already sends through an SMTP library, the SMTP relay may be the fastest route. If you need statistics, list management and webhooks in the same integration, the API is usually the better fit. Our comparison of API vs SMTP goes into detail.
Security and data residency
Transactional emails often contain personal and financial information. Mailpro encrypts connections with TLS 1.3 and hosts data in Switzerland on private infrastructure, outside US jurisdiction. The Digital Personal Data Protection Act 2023 allows transfers abroad unless the Central Government restricts a destination country, and it requires reasonable security safeguards, with penalties of up to ₹250 crore where a breach results from failing to take them. Document your provider choice as part of your DPDP compliance records.
How integration works
- Create an account and generate API credentials in the Mailpro dashboard.
- Authenticate your domain with SPF, DKIM and DMARC so Gmail and other providers trust your messages.
- Build your templates, keeping transactional templates free of promotional content.
- Call the API from your backend, whether it is written in Node.js, Python, PHP, Java or another language that can make HTTPS requests.
- Register a webhook endpoint to receive delivery and bounce events.
- Test with internal addresses on Gmail and at least one other provider, then go live.
Good practice for Indian senders
- Use a subdomain such as mail.yourbrand.in for transactional traffic so its reputation stays separate from marketing.
- Write OTP and alert emails so the key information is in the subject and first line; many users read them in a notification preview.
- Show amounts in ₹ with the same format your app uses, and state times in IST.
- If you serve users in several Indian languages, send transactional emails in the language they chose in your app.
- Keep marketing consent separate. The Digital Personal Data Protection Act 2023 requires specific consent for marketing, even for existing users.
Documentation and resources
- The API documentation covers authentication, endpoints and examples.
- The webhooks documentation explains event payloads.
- The FAQ on delivery status for transactional email explains how to track each message.
- More answers are in the SMTP and API FAQ, and the API overview summarises features.
You can start with 500 free credits and pay by sends rather than by stored contacts.