Legacy campaigns
The routes of the previous Emelia campaign system, email only or LinkedIn only. Deprecated, still working for existing integrations.
Deprecated
These routes belong to the previous campaign system, where a campaign was either email only or LinkedIn only. They keep working for existing integrations, but they are not developed any more. Every new integration should use the Campaigns routes (/advanced/...): every campaign of the current app is multichannel.
| Legacy system | Routes | Replaced by |
|---|---|---|
| Email campaigns | /emails/campaigns..., /emails/campaign/contacts, /emails/contacts, /emails/test, /stats | Campaigns with EMAIL steps |
| LinkedIn campaigns | /linkedin/campaigns..., /linkedin/campaign/contacts, /stats/linkedin | Campaigns with LinkedIn steps |
The legacy campaigns are separate objects: a legacy campaign id does not work on the /advanced/... routes, and the other way round.
What differs from the current routes
- Envelopes. The contact listings answer
{ "success": true, "list": [...], "count": 42 }, with apagethat starts at 0. - Statistics.
GET /statsandGET /stats/linkedinanswer a flat summary by default, and{ global, steps }withdetailed=true(the string). An unknown campaign answers401, not400. - Sequences. The steps are an ordered array, not a tree, and every step after the first needs a
delay.amountabove 0. - Intervals.
minIntervalandmaxIntervalof the email schedule are in seconds.daysgoes from 0 (Monday) to 6 (Sunday), as everywhere. - Errors. Most errors are plain sentences with a
400, like on the rest of the main API.
The blacklist routes also start with /emails/ but are not legacy: they apply to every campaign.