> ## Documentation Index > Fetch the complete documentation index at: https://inbound.new/docs/llms.txt > Use this file to discover all available pages before exploring further. # Reply to an email > Reply to an email or thread. Accepts either an email ID or thread ID (replies to latest message in thread). Supports reply all functionality. ## OpenAPI ````yaml https://app.stainless.com/api/spec/documented/inbound/openapi.documented.yml post /api/e2/emails/{id}/reply openapi: 3.1.0 info: title: Inbound Email API description: >+ # Inbound API The Inbound API allows you to manage email infrastructure programmatically - domains, email addresses, webhooks, and more. ## Authentication All API requests require a Bearer token in the Authorization header: ```bash curl -H "Authorization: Bearer YOUR_API_KEY" \ https://inbound.new/api/e2/domains ``` ## Base URL ``` https://inbound.new/api/e2 ``` ## Quick Start 1. **Create a domain** - Register your domain with Inbound 2. **Configure DNS** - Add the provided DNS records to your domain 3. **Create an email address** - Set up addresses to receive emails 4. **Create an endpoint** - Configure where emails are delivered (webhook, forwarding, etc.) version: 2.0.0 servers: - url: https://inbound.new description: Production API server security: - bearerAuth: [] tags: - name: Webhooks description: Webhooks sent by Inbound to your configured endpoints when events occur. - name: Emails description: >- Send, list, and manage emails. Supports immediate sending, scheduling, replies, and retry functionality. - name: Mail description: >- Inbox and thread views for received emails. Filter by domain, address, or search. - name: Domains description: >- Manage domains for sending and receiving emails. Domains must be verified via DNS before use. - name: Endpoints description: >- Configure where incoming emails are delivered - webhooks, email forwarding, or custom handlers. - name: Email Addresses description: Create and manage email addresses on your verified domains. - name: Attachments description: Download email attachments using authenticated requests. paths: /api/e2/emails/{id}/reply: post: tags: - Emails summary: Reply to an email description: >- Reply to an email or thread. Accepts either an email ID or thread ID (replies to latest message in thread). Supports reply all functionality. operationId: postApiE2EmailsByIdReply parameters: - name: id in: path required: true schema: description: Email ID or Thread ID to reply to type: string requestBody: required: true content: application/json: schema: type: object properties: from: description: Sender email address type: string to: description: Recipient email address(es) - defaults to original sender anyOf: - type: string - type: array items: type: string subject: description: 'Email subject - defaults to Re: original subject' type: string html: description: HTML content of the email type: string text: description: Plain text content of the email type: string headers: description: Custom email headers type: object patternProperties: ^(.*)$: type: string attachments: type: array items: type: object properties: filename: type: string content: type: string content_type: type: string path: type: string required: - filename - content reply_all: description: Include original CC recipients type: boolean tags: type: array items: type: object properties: name: type: string value: type: string required: - name - value required: - from application/x-www-form-urlencoded: schema: type: object properties: from: description: Sender email address type: string to: description: Recipient email address(es) - defaults to original sender anyOf: - type: string - type: array items: type: string subject: description: 'Email subject - defaults to Re: original subject' type: string html: description: HTML content of the email type: string text: description: Plain text content of the email type: string headers: description: Custom email headers type: object patternProperties: ^(.*)$: type: string attachments: type: array items: type: object properties: filename: type: string content: type: string content_type: type: string path: type: string required: - filename - content reply_all: description: Include original CC recipients type: boolean tags: type: array items: type: object properties: name: type: string value: type: string required: - name - value required: - from multipart/form-data: schema: type: object properties: from: description: Sender email address type: string to: description: Recipient email address(es) - defaults to original sender anyOf: - type: string - type: array items: type: string subject: description: 'Email subject - defaults to Re: original subject' type: string html: description: HTML content of the email type: string text: description: Plain text content of the email type: string headers: description: Custom email headers type: object patternProperties: ^(.*)$: type: string attachments: type: array items: type: object properties: filename: type: string content: type: string content_type: type: string path: type: string required: - filename - content reply_all: description: Include original CC recipients type: boolean tags: type: array items: type: object properties: name: type: string value: type: string required: - name - value required: - from responses: '200': description: Response for status 200 content: application/json: schema: type: object properties: id: type: string message_id: type: string aws_message_id: type: string replied_to_email_id: type: string replied_to_thread_id: type: string is_thread_reply: type: boolean required: - id - message_id - aws_message_id - replied_to_email_id - is_thread_reply '400': description: Response for status 400 content: application/json: schema: type: object properties: error: type: string required: - error '401': description: Response for status 401 content: application/json: schema: type: object properties: error: type: string required: - error '403': description: Response for status 403 content: application/json: schema: type: object properties: error: type: string required: - error '404': description: Response for status 404 content: application/json: schema: type: object properties: error: type: string required: - error '429': description: Response for status 429 content: application/json: schema: type: object properties: error: type: string required: - error '500': description: Response for status 500 content: application/json: schema: type: object properties: error: type: string required: - error x-codeSamples: - lang: JavaScript source: |- import Inbound from 'inboundemail'; const client = new Inbound({ apiKey: process.env['INBOUND_API_KEY'], // This is the default and can be omitted }); const response = await client.emails.reply('id', { from: 'from' }); console.log(response.id); components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API Key description: >- Your Inbound API key. Include it in the Authorization header as: Bearer ````