Email campaigns
The routes of the previous email only campaigns. Deprecated, still working for existing integrations.
Deprecated
These routes manage the email only campaigns of the previous system. They keep working, but new integrations should create Campaigns with EMAIL steps: same sending engine, plus LinkedIn, conditions and tracking per step.
What you can still do
| Need | Route |
|---|---|
| List or read the legacy email campaigns | List campaigns, Get a campaign |
| Feed a running legacy campaign | Add a contact, Add a contact to a list |
| Update one field of a contact | Set a contact field |
| Read the results | Get activities, Get statistics |
/emails/campaign/contacts
curl -X POST https://api.emelia.io/emails/campaign/contacts \
-H "Authorization: $EMELIA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"id": "6650f1a2b839d80011c5a0f1", "contact": {"email": "claire.fontaine@nexora.io", "firstName": "Claire", "lastName": "Fontaine"}}'The contact goes to a list named after the campaign. Keys other than email, firstName, lastName and phoneNumber become custom variables. A finished campaign starts again, a running one schedules the contact at once, and an email already in the campaign is refused.
Good to know
- The listing of contacts pages from
page=0and answers{ success, list, count }. Itseventfilter must be an array:event[]=REPLIED. PATCH .../settings/globalreplaces the whole schedule.minIntervalandmaxIntervalare in seconds,dailyLimitmust be at leastdailyContact.- The steps are an ordered array. Every step after the first needs
delay.amountabove 0. GET /statsanswers401for an unknown campaign, and a flat summary unlessdetailed=true.