From 5e82d3a461bddf3fe50cbf1ac76dbad6e56253a9 Mon Sep 17 00:00:00 2001 From: Varshini Suresh Date: Thu, 16 Oct 2025 23:35:53 +0100 Subject: [PATCH 1/2] Add channel field to ticket creation endpoints MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add a new `channel` field to ticket creation and conversion endpoints in the unstable API spec. The channel field: - Accepts enum value "email" (currently the only supported value) - Only supported for customer ticket types - Defaults to "messenger" when not provided - Included in ticket response schema with both "email" and "messenger" enum values Updated schemas: - create_ticket_request - convert_conversation_to_ticket_request - ticket (response schema) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- descriptions/0/api.intercom.io.yaml | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index f423cde..fd5849e 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -13589,6 +13589,7 @@ paths: has_more: false category: Back-office is_shared: false + channel: email schema: "$ref": "#/components/schemas/ticket" '401': @@ -13626,6 +13627,7 @@ paths: ticket_attributes: _default_title_: example _default_description_: there is a problem + channel: email "/tickets/enqueue": post: summary: Enqueue create ticket @@ -13659,6 +13661,7 @@ paths: ticket_attributes: _default_title_: example _default_description_: there is a problem + channel: email responses: '200': description: Successful response @@ -18186,6 +18189,12 @@ components: description: The ID of the type of ticket you want to convert the conversation to example: '1234' + channel: + type: string + description: The channel for the ticket. Only supported for customer ticket types. Defaults to messenger if not provided. + enum: + - email + example: email attributes: "$ref": "#/components/schemas/ticket_request_custom_attributes" required: @@ -19053,6 +19062,12 @@ components: description: The ID of the team to which the ticket is assigned. If not provided, the ticket will be unassigned. example: '8' + channel: + type: string + description: The channel for the ticket. Only supported for customer ticket types. Defaults to messenger if not provided. + enum: + - email + example: email required: - ticket_type_id - contacts @@ -22007,6 +22022,13 @@ components: - Back-office - Tracker example: Customer + channel: + type: string + description: The channel for the ticket. Only supported for customer ticket types. + enum: + - email + - messenger + example: messenger ticket_attributes: "$ref": "#/components/schemas/ticket_custom_attributes" ticket_state: From f1d7338a6ecf098af2068aefdc16f94d092f2c52 Mon Sep 17 00:00:00 2001 From: Varshini Suresh Date: Thu, 16 Oct 2025 23:40:02 +0100 Subject: [PATCH 2/2] Remove channel field from convert_conversation_to_ticket_request MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The channel field should only be added to create_ticket_request and the ticket response schema, not to convert_conversation_to_ticket_request. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- descriptions/0/api.intercom.io.yaml | 6 ------ 1 file changed, 6 deletions(-) diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml index fd5849e..6ecc51f 100644 --- a/descriptions/0/api.intercom.io.yaml +++ b/descriptions/0/api.intercom.io.yaml @@ -18189,12 +18189,6 @@ components: description: The ID of the type of ticket you want to convert the conversation to example: '1234' - channel: - type: string - description: The channel for the ticket. Only supported for customer ticket types. Defaults to messenger if not provided. - enum: - - email - example: email attributes: "$ref": "#/components/schemas/ticket_request_custom_attributes" required: