Skip to content

Add skip_notifications parameter to Update Ticket endpoint#383

Open
levindixon wants to merge 2 commits intomainfrom
levin.dixon/474395-skip-notifications-update-ticket
Open

Add skip_notifications parameter to Update Ticket endpoint#383
levindixon wants to merge 2 commits intomainfrom
levin.dixon/474395-skip-notifications-update-ticket

Conversation

@levindixon
Copy link
Contributor

Why?

The skip_notifications boolean parameter works on the Update Ticket (PUT /tickets/{id}) endpoint but is missing from the OpenAPI specs. The @2.13 changelog explicitly lists it as available on "create a ticket, update a ticket, and reply to a ticket endpoints" — and CS has confirmed it works in production — but it was never added to the Update Ticket spec. This is the source-of-truth counterpart to intercom/developer-docs#744.

Intercom conversation: 215473229724012 | GitHub issue: intercom/intercom#474395

How?

Wraps the Update Ticket requestBody schema in an allOf with an inline skip_notifications property — the same pattern already used by Create Ticket — across all versions where the parameter is supported (2.13, 2.14, 2.15, and 0/Unstable).

Generated with Claude Code

levindixon and others added 2 commits February 25, 2026 13:23
The skip_notifications boolean parameter works on the Update Ticket
(PUT /tickets/{id}) endpoint but was missing from the OpenAPI specs.
This adds it to 2.13, 2.14, 2.15, and Unstable (0) using the same
allOf wrapper pattern used by Create Ticket.

Closes intercom/intercom#474395

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The allOf wrapper on Update Ticket causes Fern to generate an inline
type named UpdateTicketRequest (from x-fern-request-name), which
collides with the component schema update_ticket_request. Adding
x-fern-type-name: UpdateTicketRequestBody follows the same pattern
used by create_ticket_request → CreateTicketRequestBody.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@levindixon levindixon marked this pull request as ready for review February 25, 2026 15:46
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