From d83de96226d205153eafe86e65287bb1f66848d0 Mon Sep 17 00:00:00 2001
From: Rohit Sharma <rohit.sharma@intercom.io>
Date: Thu, 27 Aug 2026 15:51:02 +0100
Subject: [PATCH 1/2] Document setting ticket priority on the update endpoint
 (Preview)

Adds priority to the Preview update-ticket request body and example.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 descriptions/0/api.intercom.io.yaml | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml
index bac51e0..e3c3393 100644
--- a/descriptions/0/api.intercom.io.yaml
+++ b/descriptions/0/api.intercom.io.yaml
@@ -23824,6 +23824,7 @@ paths:
                   open: true
                   snoozed_until: 1673609604
                   ticket_state_id: 8498
+                  priority: high
               admin_not_found:
                 summary: Admin not found
                 value:
@@ -41297,6 +41298,18 @@ components:
           description: The ID of the admin or team to which the ticket is assigned.
             Set this 0 to unassign it.
           example: '123'
+        priority:
+          type: string
+          enum:
+          - none
+          - low
+          - medium
+          - high
+          - urgent
+          description: The priority level to set on the ticket. Accepts one of none,
+            low, medium, high, or urgent. Set none to clear an existing priority. The
+            change is attributed to admin_id, or to Operator when admin_id is omitted.
+          example: high
     update_ticket_type_attribute_request:
       description: You can update a Ticket Type Attribute
       type: object

From a12cac60ccda915e9d1c9e8457e1d5927b7e054f Mon Sep 17 00:00:00 2001
From: Rohit Sharma <rohit.sharma@intercom.io>
Date: Thu, 27 Aug 2026 15:58:06 +0100
Subject: [PATCH 2/2] Declare the 403 and 422 responses the ticket priority
 write can return

The update-ticket operation only declared 200/404/400/401, so neither error
case for the new priority field was discoverable from the spec.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 descriptions/0/api.intercom.io.yaml | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml
index e3c3393..96b5ce6 100644
--- a/descriptions/0/api.intercom.io.yaml
+++ b/descriptions/0/api.intercom.io.yaml
@@ -23801,6 +23801,34 @@ paths:
                       message: Access Token Invalid
               schema:
                 "$ref": "#/components/schemas/error"
+        '403':
+          description: Forbidden
+          content:
+            application/json:
+              examples:
+                Teammate without Inbox access:
+                  value:
+                    type: error.list
+                    request_id: 8e4a1ee0-2a4c-4a9f-9c3f-1c2b6d7e5f01
+                    errors:
+                    - code: action_forbidden
+                      message: This admin does not have Inbox access permissions
+              schema:
+                "$ref": "#/components/schemas/error"
+        '422':
+          description: Unprocessable Entity
+          content:
+            application/json:
+              examples:
+                Unrecognised priority level:
+                  value:
+                    type: error.list
+                    request_id: 3f6c9b21-7d58-4e0a-8b44-5a9e2c1d7b03
+                    errors:
+                    - code: parameter_invalid
+                      message: 'priority must be one of: none, low, medium, high, urgent'
+              schema:
+                "$ref": "#/components/schemas/error"
       requestBody:
         content:
           application/json: