# Technical workflow
___

Learn how Email integrates with your systems and how messages are delivered. Choose the integration method that best fits your needs:

- **HTTP API**: Fast, secure, and analytics-ready.
- **SMTP API**: Simple to set up and ideal for transactional email.

## HTTP API vs SMTP API

| Aspect              | HTTP API                                         | SMTP API                                         |
|---------------------|--------------------------------------------------|--------------------------------------------------|
| **Protocol**        | HTTP (RESTful API calls)                         | SMTP protocol                                    |
| **Integration**     | Modern applications, REST-friendly               | Universal, supports legacy applications          |
| **Error handling**  | Detailed JSON responses, easy debugging          | Basic SMTP response codes, limited feedback       |
| **Features**        | Advanced templates, tracking, scheduling, batch processing | Basic email sending                              |
| **Security**        | API tokens, HTTPS encryption                     | Username/password, STARTTLS encryption           |
| **Performance**     | Generally faster, better concurrency             | Slower, less scalable                            |
| **Vendor lock-in**  | Higher (proprietary API formats)                 | Lower (standardized protocol)                    |
| **Compatibility**   | Requires HTTP client support                     | Supported by almost all email clients and languages |
| **Setup complexity**| Requires API integration and authentication handling | Simple: SMTP server credentials                  |
| **Scalability**     | Better scalability with high volume and concurrency | Requires client-side queuing and retries         |

Tip  
Choose **HTTP API** if you need advanced features, analytics, and high scalability. Choose **SMTP API** for simple, universal integration with existing email clients or legacy systems.

___