Replies

Returns the lead's full email thread in chronological order: outbound emails (sent, scheduled, and unsent drafts) and inbound replies. Each item carries direction (inbound/outbound), status, and, for categorized inbound emails, the AI response category. fromAddress on an outbound email is the workspace mailbox it is sent from, and a campaign sequence email carries stepIndex (0 = initial email, 1..N = follow-ups). Unsent drafts, including AI-suggested replies awaiting human review, are marked with isDraft. An AI reply draft (isDraft true, campaignId null) can be edited with PUT /reply-drafts/{id} and sent with POST /reply-drafts/{id}/send, using its id from this list. Drafts that belong to a campaign cannot be sent this way.

Lists inbound emails (replies received from prospects) in the API key's workspace, newest first, 20 per page by default (?limit= up to 200). Filter by AI response category, campaign, lead, or a time floor. responseCategory is null while AI categorization is still pending; campaignId is null for standalone replies that could not be attributed to a campaign. This list is read-only. To answer a reply, send your own message with POST /replies/{id}/reply, or send its AI draft: edit it (PUT /reply-drafts/{id}) and send it (POST /reply-drafts/{id}/send) - the draft's current subject and body are what goes out.

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.

Lists AI-suggested reply drafts awaiting human review in the API key's workspace, newest first, 20 per page by default (?limit= up to 200). Each draft answers the inbound reply referenced by inReplyToEmailId, and to and cc show who it goes to when sent: Reply All, so everyone the prospect addressed is copied. Drafts can be edited over REST (PUT /reply-drafts/{id}) and sent (POST /reply-drafts/{id}/send) - both require the read_write scope.

Updates the subject and/or body of an AI reply draft awaiting human review. At least one field must be provided and provided fields must be non-empty. This endpoint never changes the draft's status or sends anything - use POST /reply-drafts/{id}/send once the wording is ready. Emails that are not AI reply drafts - sent or scheduled emails, inbound replies, campaign sequence templates - are refused with 409.

Schedules an AI reply draft for delivery through the conversation's sender mailbox, in the same email thread. It goes out as Reply All: to the person who wrote the reply, with everyone else they addressed (their To and Cc lines, minus your workspace's own mailboxes) in Cc, as listed in to and cc. The draft's current subject and body are what goes out, so edit first (PUT /reply-drafts/{id}) if needed. Emails that are not sendable AI reply drafts - already sent or scheduled emails, inbound replies, campaign sequence templates - are refused with 409. A draft whose conversation has no connected sender mailbox or no resolvable recipient is refused with 422.