---
ref: tool:zendesk/update-ticket
name: Update a ticket
company: company:zendesk
workflows: [workflow:support-ticket-churn-risk]
access: [api]
tags: [capability:manage-tasks, category:support, has:api]
docs: https://developer.zendesk.com/api-reference/ticketing/tickets/tickets/#update-ticket
updated: 2026-09-29
---

# Update a ticket

Changes a ticket's status, priority, assignee, tags or fields, and can add a public reply or an internal note.

Note: A `comment` with `public: true` is a reply the requester can see; `public: false` makes it an internal note. This endpoint has its own rate limit and returns 429 when it runs out.

## Set up

Use the first option your agent supports.

### API (official)

- Base URL: https://{subdomain}.zendesk.com
- Endpoint: `PUT /api/v2/tickets/{ticket_id}`
- Auth: send the header `Authorization: Bearer $ZENDESK_OAUTH_TOKEN`
- Get a key: https://developer.zendesk.com/documentation/authentication/oauth-migration/#getting-your-first-token
- Docs: https://developer.zendesk.com/api-reference/ticketing/introduction/

Note: `{subdomain}` is your Zendesk subdomain, as in `acme.zendesk.com`. Tokens from OAuth clients created since April 30, 2026 expire after 30 minutes.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.