Classic API Migration
If you are currently using the Classic API and wish to migrate to the current API, consult the following table to assess the impact.
Compatibility Matrix
| Current API | Classic API | Compatibility |
|---|---|---|
| Campaigns | Mailing | Compatible |
| N/A | Mailing (recurring) | Classic only |
| N/A | Mailing (absplit) | Classic only |
| List | List | Compatible |
| Contact | List / Record | Compatible |
| Custom Attribute | List / Fields | Compatible |
| Segment | List / Sublist | Compatible |
| Suppressed Email | SuppressionList | Compatible |
| Transactional Email | Relay | Compatible |
| Transactional Email via SMTP | N/A | Current API only |
| Log | Mailing / List / Relay Log | Compatible |
| Report | Mailing / List / Relay Log | Compatible |
| Account | Client | Compatible |
| Sub-Account | Client | Compatible |
| User | User | Compatible |
| Form | N/A | Current API only |
| Domain | Client | Compatible |
| Logo | N/A | Current API only |
| Sender | N/A | Current API only |
| N/A | TemplateV2 | Classic only |
| N/A | Trigger | Classic only |
| N/A | Permission | Classic only |
| N/A | Campaign | Classic only |
Key Differences
Available only in the current API
- Transactional Email via SMTP — send emails through the SMTP gateway
- Forms — custom subscription forms with opt-in parameters
- Sender management — dedicated sender identity and authentication
- Domain management — SPF/DKIM authentication resources
- Logo — brand customization
Available only in Classic
- Recurring mailings — automated recurring sends
- A/B split mailings — built-in split testing
- TemplateV2 — legacy template system
- Triggers — legacy automation triggers
- Permissions — legacy permission model
Partner Login
The current API provides a way to embed a Login to Cakemail button in your application. See the Partner Login guide for implementation details.