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.0ClassicCompatibility
CampaignsMailingCompatible
- n/a -Mailing with type 'recurring'Only available in Classic
- n/a -Mailing with type 'absplit'Only available in Classic
ListListCompatible
ContactList / RecordCompatible
Custom AttributeList / FieldsCompatible
SegmentList / SublistCompatible
Suppressed EmailSuppressionListCompatible
Transactional EmailRelayCompatible
Transactional Email through SMTP- n/a -Only available in Next-Gen
LogMailing / Log
List / Log
Relay / Log
Compatible
ReportMailing / Log
List / Log
Relay / Log
Compatible
AccountClientCompatible
Sub-AccountClientCompatible
UserUserCompatible
Form- n/a -Only available in Next-Gen
DomainClientCompatible
Logo- n/a -Only available in Next-Gen
Sender- n/a -Only available in Next-Gen
- n/a -TemplateV2Only available in Classic
- n/a -TriggerOnly available in Classic
- n/a -PermissionOnly available in Classic
- n/a -CampaignOnly 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.