Skip to content

Conversation

@VarshSuresh
Copy link
Contributor

@VarshSuresh VarshSuresh commented Oct 16, 2025

Why?

Towards https://github.com/intercom/intercom/issues/429620

Summary

This PR adds a new channel field to ticket creation and conversion endpoints in the unstable API specification.

Changes

  • Added channel field to create_ticket_request schema
  • Added channel field to ticket response schema

Field Details

  • Type: string (enum)
  • Supported values: "email" (currently the only supported value in request schemas)
  • Scope: Only supported for customer ticket types
  • Default behavior: Defaults to "messenger" when not provided

Modified Schemas

  1. create_ticket_request (descriptions/0/api.intercom.io.yaml:18989-18994)
  2. ticket (descriptions/0/api.intercom.io.yaml:22022-22028)

🤖 Generated with Claude Code

VarshSuresh and others added 2 commits October 16, 2025 23:35
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 <[email protected]>
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 <[email protected]>
@VarshSuresh VarshSuresh changed the title Add channel field to ticket creation endpoints Add channel field to ticket creation endpoints in Unstable Oct 16, 2025
@VarshSuresh VarshSuresh requested a review from a team October 16, 2025 22:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants