FrontApp · Schema
OutboundReplyMessage
CompanyCommunicationsCustomer ServiceShared InboxEmailMessagingCollaborationHelp Desk
Properties
| Name | Type | Description |
|---|---|---|
| to | array | List of the recipient handles who will receive this message |
| cc | array | List of the recipient handles who will receive a copy of this message |
| bcc | array | List of the recipient handles who will receive a copy of this message |
| sender_name | string | Name used for the sender info of the message |
| subject | string | Subject of the message for email message |
| author_id | string | ID of the teammate on behalf of whom the answer is sent |
| channel_id | string | Channel ID the message is sent from |
| body | string | Body of the message |
| text | string | Text version of the body for email messages |
| quote_body | string | Body for the quote that the message is referencing. Only available on email channels. |
| options | object | |
| attachments | array | Binary data of attached files. Must use `Content-Type: multipart/form-data` if specified. See [example](https://gist.github.com/hdornier/e04d04921032e98271f46ff8a539a4cb) or read more about [Attachmen |
| signature_id | string | ID of the signature to attach to this draft. Only supported for email channels; using this on other channel types returns a 403 forbidden error. If null, no signature is attached. |
| should_add_default_signature | boolean | Whether or not Front should try to resolve a signature for the message. Only applies to email channels and is ignored if signature_id is included or if author_id is omitted. Default false; |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/frontapp/main/json-schema/frontapp-outbound-reply-message-schema.json",
"title": "OutboundReplyMessage",
"x-generated": "2026-10-14",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/frontapp-core-api-openapi.yml#/components/schemas/OutboundReplyMessage",
"required": [
"body"
],
"properties": {
"to": {
"type": "array",
"description": "List of the recipient handles who will receive this message",
"items": {
"type": "string"
}
},
"cc": {
"type": "array",
"description": "List of the recipient handles who will receive a copy of this message",
"items": {
"type": "string"
}
},
"bcc": {
"type": "array",
"description": "List of the recipient handles who will receive a copy of this message",
"items": {
"type": "string"
}
},
"sender_name": {
"type": "string",
"description": "Name used for the sender info of the message"
},
"subject": {
"type": "string",
"description": "Subject of the message for email message"
},
"author_id": {
"type": "string",
"description": "ID of the teammate on behalf of whom the answer is sent"
},
"channel_id": {
"type": "string",
"description": "Channel ID the message is sent from"
},
"body": {
"type": "string",
"description": "Body of the message"
},
"text": {
"type": "string",
"description": "Text version of the body for email messages"
},
"quote_body": {
"type": "string",
"description": "Body for the quote that the message is referencing. Only available on email channels."
},
"options": {
"type": "object",
"properties": {
"tag_ids": {
"type": "array",
"description": "List of tag IDs to add to the conversation",
"items": {
"type": "string"
}
},
"archive": {
"type": "boolean",
"default": true,
"description": "Archive the conversation right when sending the message. `true` by default"
}
}
},
"attachments": {
"description": "Binary data of attached files. Must use `Content-Type: multipart/form-data` if specified. See [example](https://gist.github.com/hdornier/e04d04921032e98271f46ff8a539a4cb) or read more about [Attachments](https://dev.frontapp.com/docs/attachments-1). Max 25 MB.",
"type": "array",
"items": {
"type": "string",
"format": "binary"
}
},
"signature_id": {
"type": "string",
"description": "ID of the signature to attach to this draft. Only supported for email channels; using this on other channel types returns a 403 forbidden error. If null, no signature is attached."
},
"should_add_default_signature": {
"type": "boolean",
"description": "Whether or not Front should try to resolve a signature for the message. Only applies to email channels and is ignored if signature_id is included or if author_id is omitted. Default false;"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/frontapp-outbound-reply-message"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.