Skip to content

Document reply_to on conversation source (Preview)#595

Merged
mridulmeh merged 1 commit into
mainfrom
mridul/reply-to-conversations-api-docs
Jul 20, 2026
Merged

Document reply_to on conversation source (Preview)#595
mridulmeh merged 1 commit into
mainfrom
mridul/reply-to-conversations-api-docs

Conversation

@mridulmeh

@mridulmeh mridulmeh commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Why

Companion documentation for intercom/intercom#521116 (merged), which exposed the email Reply-To header on the Conversations API message source object. The field shipped on Preview but was never documented, so it was held out of the API 2.16 cut. This adds the OpenAPI spec entry so it can be included.

What

  • Adds a reply_to array ({ email, name }) to the conversation_source schema in the Preview spec (descriptions/0/api.intercom.io.yaml), beside the existing recipients.
  • Adds reply_to to the email-source response example.

Purely additive (22 insertions, 0 deletions). Preview only — the field is copied into 2.16 during the version cut, so no other version specs are touched here.

Companion PRs

  • Monolith (merged): intercom/intercom#521116
  • Developer docs + changelog: intercom/developer-docs#1046

Generated with Claude Code

Companion to intercom/intercom#521116. Adds the reply_to array to the
conversation_source schema and the email-source example in the Preview spec.

@geetikabagga geetikabagga left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified: adds reply_to (array of {email, nullable name}, nullable, email-only) to the conversation source schema + example. Matches AddReplyToToConversationSource. LGTM.

@mridulmeh
mridulmeh marked this pull request as ready for review July 20, 2026 09:13
@mridulmeh
mridulmeh merged commit 190ceb0 into main Jul 20, 2026
3 checks passed
@mridulmeh
mridulmeh deleted the mridul/reply-to-conversations-api-docs branch July 20, 2026 09:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants