Skip to content

Conversation

@adisan19
Copy link
Contributor

Summary

Updates the DELETE /conversations/{id} endpoint description across all API versions (0, 2.13, 2.14, 2.15) to provide clearer guidance about the permanent nature of conversation deletion.

Changes

  • Added a warning admonition box highlighting that deletion is irreversible
  • Enhanced description to clarify that:
    • Deletion is permanent and cannot be reversed
    • All sensitive data is removed (admin/user replies, attributes, uploads, related content)
    • Conversation still appears in reporting, though some data may be incomplete

Affected Versions

  • Version 0 (Unstable)
  • Version 2.13
  • Version 2.14
  • Version 2.15

Validation

  • ✅ Fern check passes with 0 errors
  • ✅ YAML syntax is valid
  • ✅ Consistent description across all versions

Type of Change

  • Documentation update (OpenAPI spec)
  • Breaking change
  • New feature
  • Bug fix

This is a documentation-only change that does not affect API functionality.

🤖 Generated with Claude Code

Enhance the description to clarify that:
- Deletion is permanent and cannot be reversed
- All sensitive data is removed (replies, attributes, uploads)
- Conversation still appears in reporting with incomplete data

This provides better clarity for API consumers about the implications
of deleting conversations.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@adisan19
Copy link
Contributor Author

🔗 Related PR in developer-docs: https://github.com/intercom/developer-docs/pull/721

This PR updates the source OpenAPI specs. The developer-docs PR syncs these changes to the public documentation site.

@adisan19 adisan19 requested review from a team February 10, 2026 14:14
@adisan19 adisan19 merged commit bb6dc17 into main Feb 10, 2026
3 checks passed
@adisan19 adisan19 deleted the adisa/update-conversation-deletion-docs branch February 10, 2026 15:54
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.

3 participants