Reply to a reply

Sends your own answer to an inbound reply, in the same email thread and from the mailbox the conversation runs through (in a conversation the prospect started, your mailbox they wrote to). The id is a reply's id from GET /replies. Only body is required. Leave to out to Reply All: the person who wrote goes in To and everyone else they addressed goes in Cc, never one of your workspace's own mailboxes. Set to to choose the recipients yourself: then to, cc and bcc are used exactly as sent (cc is only read together with to; bcc works either way), at most 20 addresses in all. There is no subject field: the answer keeps the thread's subject, with "Re: " in front, so the thread never breaks. contentType is "text" by default; send "html" only when body is HTML. An html body keeps basic formatting (paragraphs, line breaks, bold, italics, links, lists and headings); images, tables and inline styles are removed when it is sent. Merge tags such as {first_name} and spintax such as {Hi|Hello} in body are filled in when the email is sent, as in a campaign email. No signature is added: put yours in body. attachments takes at most 5 files, 10 MB in total, each as fileName plus contentBase64. The same reply can be answered more than once, which is how you send a second message in a conversation. Two limits stop a client that went wrong: an identical body to the same reply within 60 seconds is refused (409), so a retry after a timeout never sends twice, and one reply takes at most 20 answers in any hour (429, with a Retry-After header that says in how many seconds the next one is accepted). The answer is scheduled and goes out within about a minute; GET /leads/{id}/conversation shows its status move from scheduled to sent. Unknown fields are refused (400) rather than ignored. Requires the read_write scope.