Netcore CPaaS is a cloud-based email delivery service that delivers highly personalized transactional emails to the inbox within seconds of your customer’s transaction. Netcore CPaaS dashboard helps you focus on your business without the cost and complexity of owning and maintaining an email infrastructure. It manages all the technicalities like scaling the infrastructure, ISP outreach, reputation monitoring, whitelist services and real-time analytics. Netcore CPaaS dashboard offers world class deliverability expertise to ensure that your emails get delivered on time and into the inbox.
Note
- Most of the Email APIs follow a RESTful architecture.
- All API calls must be made using HTTP POST.
Netcore CPaaS dashboard provides two ways to send an email:
- through our SMTP relay.
- through our Web API.
This document will share the details of the APIs which will help you to send emails and manage your CPaaS account.
Sending Data to the API
Request data should be sent to the API by POSTing JSON objects to the appropriate endpoints. Each API's documentation will detail the specific parameters it accepts.
Although you can also send data using HTTP POST form parameters (similar to submitting an HTML form), we strongly recommend using JSON for better structure, clarity, and compatibility with most modern applications.
HTTP Response Codes
Netcore Email APIs follow standard HTTP status codes. Refer to the given table to know more.
| Status Code | Meaning | Description |
|---|---|---|
| 200 OK | Success | Request was successful. Common for GET requests. |
| 201 Created | Resource Created | A new resource was created. Example: Creating a template. |
| 202 Accepted | Request Queued | Request accepted but processing is not complete. Example: Sending email during daily limit cap. |
| 400 Bad Request | Invalid Request | Malformed syntax or invalid parameters. |
| 401 Unauthorized | Authentication Error | Missing or incorrect API Key in the Authorization header. |
| 405 Method Not Allowed | Invalid HTTP Method | The HTTP method used (GET, POST, etc.) is not allowed for this endpoint. |
| 500 Internal Server Error | Server Error | Netcore Email API failed to process the request. Retry after some time. |
Choosing Between SMTP and API
Whether to use SMTP or API for sending emails depends on your use case, technical capabilities, and the platform you’re integrating with.
| SMTP | API |
|---|---|
| Easy to integrate with any system | Offers more flexibility and control |
| No development effort required | Higher security and authentication options |
| Ideal for standard use cases or legacy systems | Better performance at scale |
| Cloud-based SMTP can be reliable | Faster response times and lower chances of failure |
| Simple setup and widely supported | More customization and real-time tracking capabilities |
Which One Should You Choose?
- Use SMTP if you’re looking for a quick, plug-and-play setup with minimal development.
- Use API if you want more control, better performance, and the ability to deeply customize your email sending workflows.
While both are effective, APIs generally offer faster processing, enhanced tracking, and a lower risk of failure—especially when dealing with high volumes or complex use cases.