[hrp]

Why?

Setting a ticket's priority is already documented, but nothing describes reading it back, so an integration that writes a level has no documented way to confirm it stuck short of fetching the underlying conversation. The ticket schema omits the field entirely, which stops being accurate once the read side ships.

How?

Adds the priority level to the Preview ticket response schema, copying the shape the conversation object already uses.

Notes for reviewers

• Affected versions: Preview only. No dated version changes.
• Draft on purpose. This should only merge once the API change has shipped, or the spec will describe a field that isn't being returned yet.
• The spec addition is byte-identical to the developer-docs copy, diffed to confirm the two stay in step.
• The five levels and the description are lifted from the conversation object's existing priority field.

Spec mirror, merge alongside this one:

• https://github.com/intercom/developer-docs/pull/1128

Follows on from:

• Document setting ticket priority on the update endpoint (Preview) #647

_{Generated with Claude Code}

[hrp]

Closing: the read-side change this documents (intercom/intercom#566184) was closed unmerged, so the API doesn't return this field. Reopen if that ships.