Fix incorrect qualified_id examples in Unstable spec#400
Closed
hitvardhan-solanki-ai wants to merge 1 commit intomainfrom
Closed
Fix incorrect qualified_id examples in Unstable spec#400hitvardhan-solanki-ai wants to merge 1 commit intomainfrom
hitvardhan-solanki-ai wants to merge 1 commit intomainfrom
Conversation
The attribute_ids example showed unqualified IDs (conversation_id) but the Unstable API requires qualified format. The qualified_id example used the wrong prefix (conversation.conversation_id instead of standard.conversation_id). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
The OpenAPI spec for the Unstable API version has incorrect examples for the
qualified_idfeature on the Reporting Data Export endpoints. This caused a customer to use the wrong attribute format, resulting in API errors.attribute_idsexample showed unqualified IDs (conversation_id) but the API requires qualified format (standard.conversation_id)qualified_idresponse example used the wrong prefix (conversation.conversation_idinstead ofstandard.conversation_id)Related:
How?
Fixed both examples in
descriptions/0/api.intercom.io.yamlto use the correct qualified_id format matching the actual API behavior.Generated with Claude Code