zinn-campaigns
PATCH /v1/email-marketing/cold/replies/{reply_id}
Mark a Unibox row read or unread, or label it.
Authentication
Send an API key as a bearer token. The key must carry the email_marketing.manage permission; a key without it is refused with 403, not 404.
Where your organisation id goes
This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.
Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X PATCH https://api.zinndigital.com/v1/email-marketing/cold/replies/{reply_id} \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ }'Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
Gated on email_marketing.manage. read is a boolean; label is one of the fixed labels (an empty string clears it). Anything else is refused with 400. 404 outside the caller's organisation.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
org_id (query) | Uuid | No | The organization this call acts on. Optional for a caller with exactly one direct membership; required for anyone with more than one — which is every reseller and every agency… |
reply_id (path) | string | Yes | — |
Request body
| Name | Type | Required | What it is |
|---|---|---|---|
read | boolean | No | — |
label | string<, interested, not_interested, meeting, later, wrong_person> | No | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
id | string | Yes | — |
mailbox_id | string | Yes | — |
sequence_id | string | No | — |
lead_id | string | No | — |
kind | string<reply, auto_reply, bounce, unsubscribe> | Yes | — |
from_email | string | Yes | — |
from_name | string | No | — |
subject | string | No | — |
snippet | string | No | The reply's own words |
received_at | string | Yes | — |
read | boolean | Yes | — |
label | string<, interested, not_interested, meeting, later, wrong_person> | Yes | — |
answer_status | string<, queued, sent, failed> | Yes | The customer's answer to this reply from the Unibox: empty when none was written, queued while it is being sent, sent, or failed (it may be sent again). |
answer_detail | string | Yes | Why a failed answer failed: mailbox (the mailbox cannot send), unavailable (it could not be started; nothing was sent), auth_<code>, smtp_<code> or network_<error>… |
answered_at | string | Yes | — |
Errors this endpoint can return
400 · 401 · 403 · 404