Expose quoted/forwarded email thread content via the public REST API | Community
Skip to main content
Submitted

Expose quoted/forwarded email thread content via the public REST API

Related products:Integrations, API & Custom Actions
  • July 22, 2026
  • 2 replies
  • 48 views

Matej Bosnjak
Forum|alt.badge.img

Hi Intercom team,

When a customer replies to an outbound email and includes a quoted or forwarded email thread, that content is currently only accessible via a private Ember endpoint and is not returned by GET /conversations/{conversation_id}.

For teams building automation or AI on top of the Intercom API, this is a significant blind spot. The quoted thread often contains the most relevant context - original invoices, prior correspondence, or forwarded messages from third parties.

What we are asking for: Expose the quoted/forwarded email body content as part of the conversation parts response in the public REST API, either inline or as a separate field on the relevant conversation part.

Use case: AI billing support agent that needs to read the full case context, including any email history the customer has included in their reply, in order to classify and respond accurately.
Connected community thread: 

We would love to see this prioritised and are happy to provide further details or test any beta implementation.

Best regards,

Matej Bosnjak

reev

2 replies

  • New Participant
  • August 26, 2026

Massive plus one! We are having exactly the same problem. This is critical context to be missing.


Matej Bosnjak
Forum|alt.badge.img
  • Author
  • Connector
  • September 14, 2026

Intercom has now confirmed to us that quoted and forwarded email content is officially available through the public REST API:

 

GET /conversations/{conversation_id}?include_email_history=true

The response includes the content in:

 

source.email_message_metadata.history

The history field contains the quoted or forwarded thread as HTML. It is only available on the conversation’s source email metadata, not in the individual conversation parts, and the parameter is not supported on list or search endpoints.