From ba10b4668810d66b1a832db8cb3d53bdb2d5f07e Mon Sep 17 00:00:00 2001 From: Hitvardhan Singh Solanki Date: Mon, 16 Mar 2026 11:26:48 +0000 Subject: [PATCH] Fix incorrect qualified_id examples in Unstable API spec 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) --- descriptions/0/api.intercom.io.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index 854f7c7..851f9d8 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -1643,7 +1643,7 @@ paths: description: List of attribute identifiers to include in the export. Requires qualified_id format (e.g., "people.Brand", "standard.conversation_id"). Use the qualified_id returned from the get_datasets response. items: type: string - example: [conversation_id, conversation_started_at] + example: [standard.conversation_id, timestamp.conversation_started_at] start_time: type: integer format: int64 @@ -1866,7 +1866,7 @@ paths: qualified_id: type: string description: A namespaced identifier that uniquely identifies the attribute across all types. Format is "prefix.name" (e.g., "people.Brand", "conversation.Brand"). Required when calling the enqueue endpoint. - example: conversation.conversation_id + example: standard.conversation_id name: type: string example: Conversation ID