Zby Zendesk
Update a ticket
Changes a ticket's status, priority, assignee, tags or fields, and can add a public reply or an internal note.
Description
Send only the properties to change, in a `ticket` object. A `comment` with `public: true` is a reply the requester can see; `public: false` is an internal note. A ticket holds at most 5,000 comments. This endpoint has its own rate limit, separate from the account-wide one, and returns 429 when it runs out.
update-ticket.md
Update a ticket
Changes a ticket's status, priority, assignee, tags or fields, and can add a public reply or an internal note.
Send only the properties to change, in a ticket object. A comment with
public: true is a reply the requester can see; public: false is an
internal note. A ticket holds at most 5,000 comments. This endpoint has its
own rate limit, separate from the account-wide one, 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/
Before doing anything else, make one read-only call to confirm access.
Rules
- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.
Built from these files in the repository
The layout and the rules come from lib/catalog/render-markdown.ts, the set-up wording from lib/catalog/render-access.ts.
Ways in
| Route | Source | Call | Required | Docs |
|---|---|---|---|---|
| Official | PUT /api/v2/tickets/{ticket_id} | API key in $ZENDESK_OAUTH_TOKEN | Docs |