Reply in a thread
Sends from the mailbox that owns the conversation — the prospect always sees a reply from the address that emailed them. Free of credits. Attachments ride on the email (multipart form). INB-09: channel overrides which channel the reply goes out on when both identities are known; absent, the thread’s own channel decides. A pick the thread cannot honour returns 422 with the reason. INB-10: to redirects the reply (first address is the To line, the rest ride as CC) and bcc rides blind; both are email-only. INB-12: omit_signature skips the mailbox signature append, for a composer whose body already carries it as visible text.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
1 - 10000020002000Which surface a conversation happens on.
Threads are contact-scoped, not channel-scoped, so this says how a thread is REACHED rather than partitioning the inbox: a reply arrives, is classified and stops the cadence identically either way, and only the send path differs.
email, linkedin 9982000Response
Successful Response
NEW-A: hard vs soft severity of a BOUNCE message.
Only HARD marks the contact bounced (§29's condition, the enrolment analytics bounce rate, §57's per-message outcome) — SOFT still fills the Bounces view and never looks like a reply, but the address may still be reachable, so the cadence is left alone.
hard, soft INB-25: this message's own channel. Threads merge channels, so the reader captions each message by what it actually is — a LinkedIn DM involves no email addresses.
email, linkedin outbound, inbound What an inbound message turned out to be.
REPLY stops the cadence; BOUNCE (a DSN) marks the contact bounced and never looks like a reply; OUT_OF_OFFICE never stops anything and defers the cadence to the stated return when one is parsed.
reply, bounce, out_of_office Whether a message has actually left.
Only meaningful on LinkedIn. An email row is written after the provider
accepted it, so it is SENT the moment it exists; a LinkedIn reply is
written when it is QUEUED, and cannot become SENT until the customer's
own browser has delivered it. Showing the two the same way would have the
product assert a delivery it has no evidence for.
sent, queued, failed INB-09: the sender's raw HTML part; sanitise before rendering.
§78: the sequence this message was sent from, when it came from one.
§78: which step sent this message — carried per-message (not just on the thread) because a contact re-enrolled in a different sequence keeps their earlier messages' own sequence/step, distinct from the thread's current one.