--- title: "Reply to an email" method: POST path: "/api/v2/emails/reply" tags: ["Email"] --- # Reply to an email `POST /api/v2/emails/reply` Send a reply to an email. This endpoint can be used to send an email only as a reply to an existing email. In order to reply to an email, please specify the `reyply_to_uuid` field, and your email will be sent as a reply to that email. The `reyply_to_uuid` field represents the `id` field of an existing email, which is being returned to you in all the `/email` endpoints Requires one of the following scopes: `emails:create`, `emails:all`, `all:create`, `all:all` ## Request body - object - `eaccount` string, required — The email account that will be used to send this email. It has to be an email account connected to your workspace - `reply_to_uuid` string, required — The id of the email to reply to - `subject` string, required — Subject line of the email message - `body` object, required — The email body. You can specify either the `html` or the `text` field, or both - `html` string — HTML body of the email message - `text` string — Text body of the email message - `additional_recipients` string[] — Optional list of extra recipient email addresses to include in the reply, in addition to the default recipient (the sender of the email being replied to). - `cc_address_email_list` string — Comma-separated list of CC email addresses - `bcc_address_email_list` string — Comma-separated list of BCC email addresses - `reminder_ts` string, date-time — If provided then a reminder will be attached to this email, you will see this reminder in the Unibox in the web app - `assigned_to` string, uuid — The user id assigned to the lead ## Response `200` The requested Email - Email — A campaign email, a reply, a manually sent email, or any other email that's visible in the Unibox - `id` string, uuid, required — A Unique identifier - `timestamp_created` string, date-time, required — Timestamp when the email was added to our database. This is not the timestamp of the email itself, since the email could have been sent at a different time. Please check the `timestamp_email` field for the timestamp of the email. - `timestamp_email` string, date-time, required — The timestamp of the email, as provided by the email server. Please note that the timestamp is not always accurate, as it can be manipulated by the sender or the email server. - `message_id` string, required — Unique email ID from the email server - `subject` string, required — Subject line of the email message - `from_address_email` string, email, nullable — The sender email address, populated based on the eaccount - `to_address_email_list` string, required — Comma-separated list of recipient email addresses - `cc_address_email_list` string, nullable — Comma-separated list of CC email addresses - `bcc_address_email_list` string, nullable — Comma-separated list of BCC email addresses - `reply_to` string, nullable — Reply-to email address - `body` object, required — An object containing the email body in HTML and text format - `text` string — Text content of the email - `html` string — HTML content of the email - `organization_id` string, uuid, required — The workspace ID - `campaign_id` string, uuid, nullable — The id of the campaign that the email is associated with (it can be null for manually sent emails) - `subsequence_id` string, uuid, nullable — The id of the campaign subsequence that the email is associated with (it can be null for manually sent emails) - `list_id` string, uuid, nullable — The id of the list (if the lead is part of a list) - `lead` string, nullable — The email address of the lead that the email is associated with - `lead_id` string, uuid, nullable — The lead id (if any) - `eaccount` string, required — The email account that was used to send the email. This needs to be validated to make sure it exists in the user workspace - `ue_type` 1 | 2 | 3 | 4, nullable — Email type based on the life cycle of the email - `step` string, nullable — The campaign step that the email is associated with - `is_unread` number, nullable — Indicates if the email is unread - `is_auto_reply` number, nullable — Indicates if the email is an auto-reply. 0 (zero) - is false, and 1 is true - `reminder_ts` string, date-time, nullable — Timestamp for the reminder. - `ai_interest_value` number, nullable — AI interest value - `ai_assisted` number, nullable — Indicates if AI assistance was used - `is_focused` number, nullable — Indicates if the email is focused (is in the primary tab in the Unibox) - `i_status` number, nullable — Indicates the interest status of the email - `thread_id` string, uuid, nullable — Identifier for the email thread. All the emails in the same thread have the same thread ID - `content_preview` string, nullable — A short preview of the email content (usually the first few lines of the email) - `attachment_json` object, nullable — Attachment metadata for the email. This field is null when there are no attachments. - `files` object[], required - `filename` string, required — Attachment file name - `size` number — Attachment file size in bytes - `type` string — Attachment MIME type - `url` string, uri — Download URL when available - `error` string, nullable — Error description when the attachment failed to upload - `from_address_json` unknown - `to_address_json` unknown - `cc_address_json` unknown - `ai_agent_id` string, uuid, nullable — ID of the AI agent that sent this email (if applicable) ## Other responses - `401` — This request is unauthorized (either the Authorization header is missing or invalid, or the API key has been revoked) - `402` — This request cannot be fulfilled because the workspace does not have an active paid plan - `404` — The requested resource was not found - `429` — You have exceeded the rate limit. Please check the rate limit docs for more information. --- [API](https://skmtc.net/instantly/apis/api-explorer.md) · [All operations](https://skmtc.net/instantly/apis/api-explorer/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/instantly/api-explorer/revisions/378d1e253fe7/schema)