---
title: "Get a task comment"
method: GET
path: "/tasks/{task_id}/task-comments/{task_comment_id}"
tags: ["Tasks"]
---

# Get a task comment

`GET /tasks/{task_id}/task-comments/{task_comment_id}`

Get a specific task comment.

## Path parameters

- `task_comment_id` string, required
- `task_id` string, required

## Headers

- `Accept-Language` string

## Response `200`

OK

- object
  - `data` TaskComment — Task comment.
    - `task_comment_id` string — The unique ID of the task comment.
    - `task_id` string, required — The unique ID of the task. [GET /tasks](https://carecloud.readme.io/reference/gettasks)
    - `text` string, required — Text of the comment.
    - `last_change` string — Date and time of the last comment change. *(YYYY-MM-DD HH:MM:SS)*
    - `state` 0 | 1 | 2 — State of the event type. *Possible values are: 0 - deleted / 1 - active / 2 - non active*

## Other responses

- `400` — Bad input parameter. The response body's `error.error_data.invalid_params[]` array lists the parameters that caused the failure, each carrying a `reason` code. See the `BadRequestErrorBody` schema for the generic reason taxonomy. Operations with domain-specific business rules document additional reasons at the operation level.
- `401` — The client has invalid credentials or auth token.
- `403` — The client does not exist or the client tried to access an unauthorized property or resource.
- `404` — The resource was not found.
- `405` — The resource does not support the specified HTTP method.
- `429` — Too many requests - more than the resource limit.
- `500` — Server is not working as expected.
- `503` — Temporary state when the service is temporarily unavailable, overloaded or there is a maintenance window.

---

[API](https://skmtc.net/crmcarecloud/apis/rest-api-reference.md) · [All operations](https://skmtc.net/crmcarecloud/apis/rest-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/crmcarecloud/rest-api-reference/versions/329c06dbf8d9/schema)