Classic API compatibility
If you are currently using the Classic API and wish to migrate to Next-gen, please first consult the following table in order to properly assess the impact of your migration.
Next-gen v1.0 | Classic | Compatibility |
|---|---|---|
Campaigns | Mailing | Compatible |
| Mailing with type 'recurring' | Only available in Classic |
| Mailing with type 'absplit' | Only available in Classic |
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 through SMTP |
| Only available in Next-Gen |
Log | Mailing / Log | Compatible |
Report | Mailing / Log | Compatible |
Account | Client | Compatible |
Sub-Account | Client | Compatible |
User | User | Compatible |
Form |
| Only available in Next-Gen |
Domain | Client | Compatible |
Logo |
| Only available in Next-Gen |
Sender |
| Only available in Next-Gen |
| TemplateV2 | Only available in Classic |
| Trigger | Only available in Classic |
| Permission | Only available in Classic |
| Campaign | Only available in Classic |
Cakemail Next-gen also provides a way to add a Login to Cakemail or Login to Email Marketing from inside your app or control panel.
Its implementation differs from that of Cakemail Classic, and instructions can be found in the Login to Next-gen from inside your app guide.
Updated about 1 month ago