[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)

# Reply to ticket

> Add a public reply to a ticket and optionally set its status in the same call. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/zendesk/reply_to_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)

Add a public reply to a ticket and optionally set its status in the same call.

Zendesk API: https://cotlet.dev/docs/api/zendesk.md

`POST https://cotlet.dev/api/v1/zendesk/tickets/{ticket_id}/replies`

Access: write. Confirm: waits for the user's OK before it runs.

Adds a public comment to the ticket, which emails the requester unless the notification trigger is disabled in your Zendesk. A comment cannot be removed afterwards. Set status in the same call to move the ticket to pending or solved with the reply. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from search_tickets or list_view_tickets. |
| `body` | string | yes | Reply text, sent to the requester. |
| `status` | enum | no | open, pending, hold or solved. Default: leave the status as it is. hold only if an admin enabled On-hold. |

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/zendesk/tickets/48102/replies \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"Hi Dana, just checking in. To fix the export we still need the exact error text you see after clicking Export. A screenshot works too.","status":"pending"}'
```

**Python**

```python
result = client.call("zendesk", "reply_to_ticket", {"ticket_id":48102,"body":"Hi Dana, just checking in. To fix the export we still need the exact error text you see after clicking Export. A screenshot works too.","status":"pending"})
```

**Node.js**

```js
const result = await cotlet.call('zendesk', 'reply_to_ticket', {"ticket_id":48102,"body":"Hi Dana, just checking in. To fix the export we still need the exact error text you see after clicking Export. A screenshot works too.","status":"pending"});
```

**CLI**

```bash
cotlet call zendesk reply_to_ticket --data '{"ticket_id":48102,"body":"Hi Dana, just checking in. To fix the export we still need the exact error text you see after clicking Export. A screenshot works too.","status":"pending"}'
```

## Example response

```json
{
  "ticket_id": 48102,
  "comment_id": 9120044471,
  "public": true,
  "status": "pending",
  "created_at": "2026-10-16T09:00:00Z"
}
```

Previous: [List agents](https://cotlet.dev/docs/api/zendesk/list_agents.md)
Next: [Add internal note](https://cotlet.dev/docs/api/zendesk/add_internal_note.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.