Skip to content

Document no-reply conversation population on Reporting Data Export (Preview)#544

Draft
neddinn wants to merge 1 commit into
mainfrom
stephen.s/no-reply-conversation-docs
Draft

Document no-reply conversation population on Reporting Data Export (Preview)#544
neddinn wants to merge 1 commit into
mainfrom
stephen.s/no-reply-conversation-docs

Conversation

@neddinn

@neddinn neddinn commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Why

The Reporting Data Export API is gaining a no-reply-inclusive conversation population on the Preview version, as part of the Reporting what's in the inbox project. This documents the changed population semantics in the Preview OpenAPI spec.

Scope: only the conversation dataset is affected. On Preview, the export returns all conversations including those that never received a user reply; earlier versions return only replied conversations. Other datasets are unchanged.

What

Adds a description to POST /export/reporting_data/enqueue in descriptions/0/api.intercom.io.yaml (Preview) documenting the new population.

DRAFT — do not merge before the no-reply data is GA (target 25 Jun, intercom/intercom#519258). The Preview spec would otherwise advertise a population the index can't yet return.

Related

  • Monolith promotion PR: intercom/intercom#520233
  • Companion developer-docs PR: (to be linked)
  • Tracking issue: intercom/intercom#520253
  • Project tracker: intercom/intercom#511395

Generated with Claude Code

…review)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

1 participant