Graduate list handling events endpoint to stable 2.15#560
Merged
Conversation
dac01d8 to
daf3b5f
Compare
Apexinsideapex
approved these changes
Jun 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Graduates the Conversations → list handling events endpoint (
GET /conversations/{id}/handling_events,listHandlingEvents) from Preview to stable 2.15 in the source-of-truth spec.Adds to
descriptions/2.15/api.intercom.io.yaml:handling_eventandhandling_event_listresponse schemasteammate_referenceschema (dependency of the response — previously only indescriptions/0/)Endpoint is kept in
descriptions/0/(Unstable) too — it remains served onIntercom-Version: Preview, so existing Preview integrations are unaffected.Additions-only (124 insertions, 0 deletions); spec parses as valid YAML; all
$refs resolve within the 2.15 spec (errorandintercom_versionalready present).Postman collections regenerate automatically on merge to main (
generate_postman_collection.yml). SDKs are unaffected (Fern stable source is 2.14; the endpoint is already in the unstabledescriptions/0/SDK source).Why
Per #team-integration-capabilities thread, the API team confirmed the endpoint can go straight into the current stable version (2.15). Requesting customer: Preply.
Companion PRs (three-repo set)
AddHandlingEventsApiinto the 2.15 version blockLand this PR first/alongside #987 so the published docs aren't hand-edited ahead of their source.