From 4da89d7cc88f08d774da727c574c2b72502e64cc Mon Sep 17 00:00:00 2001
From: Hiten Parmar <hiten.parmar@intercom.io>
Date: Fri, 28 Aug 2026 10:25:25 -0700
Subject: [PATCH] Document reading a ticket's priority back from the API
 (Preview)

Mirrors the developer-docs spec addition so the two stay in step. The
ticket object returns priority with the same levels the update endpoint
already accepts.

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

diff --git a/descriptions/0/api.intercom.io.yaml b/descriptions/0/api.intercom.io.yaml
index 96b5ce6..aa2d2bf 100644
--- a/descriptions/0/api.intercom.io.yaml
+++ b/descriptions/0/api.intercom.io.yaml
@@ -39966,6 +39966,17 @@ components:
             change. Returns null if no state change history exists. Useful for tracking
             state transitions for reporting and compliance.
           example: '7493'
+        priority:
+          type: string
+          enum:
+          - none
+          - low
+          - medium
+          - high
+          - urgent
+          description: The priority level of the ticket. Returns one of none, low,
+            medium, high, or urgent.
+          example: high
     ticket_deleted:
       title: Ticket Deleted
       type: object