Skip to content

Add qualified_id field to Reporting Data Export API schema#366

Open
hitvardhan-solanki-ai wants to merge 2 commits intomainfrom
hitvardhansinghsolanki/add-qualified-id-reporting-export
Open

Add qualified_id field to Reporting Data Export API schema#366
hitvardhan-solanki-ai wants to merge 2 commits intomainfrom
hitvardhansinghsolanki/add-qualified-id-reporting-export

Conversation

@hitvardhan-solanki-ai
Copy link

Updates the Unstable OpenAPI spec to include the new qualified_id field for attribute disambiguation in the get_datasets response.

Main fix: https://github.com/intercom/intercom/pull/469311

@hitvardhan-solanki-ai hitvardhan-solanki-ai requested review from a team February 11, 2026 15:43
Updates the Unstable OpenAPI spec to include the new qualified_id field
for attribute disambiguation in the get_datasets response.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The public_id fallback has been removed from find_attribute, so
attribute_ids must use qualified_id format (e.g., "standard.conversation_id")
instead of plain public_id (e.g., "conversation_id").

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@hitvardhan-solanki-ai hitvardhan-solanki-ai force-pushed the hitvardhansinghsolanki/add-qualified-id-reporting-export branch from 27b9285 to e27fc81 Compare February 16, 2026 13:33
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