[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Update ticket

> Change priority, status, assignee, department or tags of a ticket. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/tidio/update_ticket

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Change priority, status, assignee, department or tags of a ticket.

Tidio API: https://cotlet.dev/docs/api/tidio.md

`PATCH https://cotlet.dev/api/v1/tidio/tickets/{ticket_id}`

Access: write.

Changes the fields you pass and leaves the rest. Status is open, pending or solved and priority is low, normal or urgent. It sends no message to the customer, and a wrong change is undone by calling it again with the old values, so it needs no confirmation by default. It returns the ticket as it is after the change.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets. |
| `status` | enum | no | open, pending or solved. |
| `priority` | enum | no | low, normal or urgent. |
| `assignee` | string | no | Operator name from list_operators. |
| `department` | string | no | Department name from list_operators. |
| `add_tags` | string[] | no | Ticket tags to add, from Settings > Tags. |
| `remove_tags` | string[] | no | Ticket tags to remove. |

## Request

**cURL**

```bash
curl -X PATCH https://cotlet.dev/api/v1/tidio/tickets/10477 \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"priority":"urgent","department":"Billing","add_tags":["refund"]}'
```

**Python**

```python
result = client.call("tidio", "update_ticket", {"ticket_id":10477,"priority":"urgent","department":"Billing","add_tags":["refund"]})
```

**Node.js**

```js
const result = await cotlet.call('tidio', 'update_ticket', {"ticket_id":10477,"priority":"urgent","department":"Billing","add_tags":["refund"]});
```

**CLI**

```bash
cotlet call tidio update_ticket --data '{"ticket_id":10477,"priority":"urgent","department":"Billing","add_tags":["refund"]}'
```

## Example response

```json
{
  "ticket_id": 10477,
  "status": "open",
  "priority": "urgent",
  "assignee": null,
  "department": "Billing",
  "tags": [
    "refund"
  ]
}
```

Previous: [Reply in live chat](https://cotlet.dev/docs/api/tidio/reply_in_conversation.md)
Next: [Update contact](https://cotlet.dev/docs/api/tidio/update_contact.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.