Store your audience in Delivrie: create and import contacts, custom properties, segments for broadcasts and automations, and topics for granular unsubscribes.
Contacts are the people you send broadcasts and automations to. They belong to your team, and each email address appears once.
POST /contacts creates a contact, or updates it if the email already exists, so it's safe to call on every sign-up:
curl -X POST https://delivrie.io/api/contacts \
-H "Authorization: Bearer $DELIVRIE_API_KEY" -H "Content-Type: application/json" \
-d '{
"email": "ada@example.com",
"first_name": "Ada",
"last_name": "Lovelace",
"properties": { "plan": "pro", "city": "London" },
"segments": ["SEGMENT_ID"]
}'await delivrie.contacts.create({ email: "ada@example.com", first_name: "Ada", properties: { plan: "pro" } });Get, update or delete a contact by id or email address:
curl https://delivrie.io/api/contacts/ada@example.com -H "Authorization: Bearer $DELIVRIE_API_KEY"
curl -X PATCH https://delivrie.io/api/contacts/ada@example.com \
-H "Authorization: Bearer $DELIVRIE_API_KEY" -H "Content-Type: application/json" \
-d '{ "properties": { "plan": "scale" }, "unsubscribed": false }'properties in an update are merged into the existing ones; other properties are kept.
Upload a CSV in Contacts → Import. Map columns to email, first name, last name and properties, and choose a segment to add everyone to. Only import people who agreed to hear from you.
Properties hold anything you want to personalise or filter by: plan, city, signup date. Define them, with a type and fallback value, in Contacts → Properties. GET /contact-properties lists them. Use them in broadcasts as {{plan}}.
Segments are named groups of contacts. Broadcasts go to a segment, and automations can start when someone joins one.
| Request | What it does |
|---|---|
POST /segments with { "name": "Beta users" } | Create a segment |
GET /segments | List segments |
POST /segments/:id/contacts with { "contacts": ["ada@example.com", { "email": "sam@example.com", "first_name": "Sam" }] } | Add contacts, creating any that don't exist |
DELETE /segments/:id | Delete the segment (the contacts stay) |
Topics let people opt out of one kind of email (say, product updates) without leaving everything. Create them in Contacts → Topics with a default of opt-in or opt-out, then pick a topic when you create a broadcast. The unsubscribe page shows each topic as its own switch. GET /topics lists them.
A contact with unsubscribed: true gets no broadcasts. It happens when they click unsubscribe, when they mark a broadcast as spam, or when you set it. Transactional emails sent with POST /emails aren't affected; they're for messages the person needs, like receipts.