Skip to content

Add API version 2.15 with conversation_rating behavior documentation#358

Open
markdennis22 wants to merge 2 commits intomainfrom
document-conversation-rating-2.15-behavior
Open

Add API version 2.15 with conversation_rating behavior documentation#358
markdennis22 wants to merge 2 commits intomainfrom
document-conversation-rating-2.15-behavior

Conversation

@markdennis22
Copy link
Contributor

Why?

Intercom API PR #456366 changed the behavior of conversation_rating in version 2.15. Previously, it returned the latest rating by ID regardless of completion status. Now it returns the latest completed rating (one with an actual value), falling back to latest rating if none exist. This behavior change needs to be documented in the OpenAPI spec so API consumers understand the version-specific behavior.

How?

Adds the 2.15 API spec with an updated conversation_rating schema description that explains the version-specific behavior difference.

Generated with Claude Code

markdennis22 and others added 2 commits February 5, 2026 14:07
Adds the API spec for version 2.15 and documents the behavior change
where conversation_rating now returns the latest completed rating
(one with an actual value) instead of just the latest by ID.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Apply the same versioning documentation to the Unstable API spec.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
description: |-
The Conversation Rating object which contains information on the rating and/or remark added by a Contact and the Admin assigned to the conversation.

Note: Starting from version 2.15, this returns the latest completed conversation rating (one with an actual rating value). If no completed ratings exist, it falls back to the latest rating. In earlier versions, this returns the latest rating by ID regardless of completion status.
Copy link
Contributor

Choose a reason for hiding this comment

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

Curious about this note here. Why do you think we need this here?

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