---
title: "Update Request"
method: PUT
path: "/api/v2/requests/{request_id}"
tags: ["Requests"]
---

# Update Request

`PUT /api/v2/requests/{request_id}`

Updates a request with a comment or collaborators (cc's). The end user who created the request can also use it to mark the request as solved. The endpoint can't be used to update other request attributes.

#### Writable properties
This endpoint can only update the following properties in the request.

| Name                     | Type    | Required | Description                                          |
| ------------------------ | ------- | -------- | ---------------------------------------------------- |
| comment                  | object  | no       | Adds a comment to the request. See [Request comments](#request-comments) |
| solved                   | boolean | no       | Marks the request as solved. Example: `{"request": {"solved": "true"}}`. End users can mark requests as solved only if the request's `can_be_solved_by_me` property is true. The property is true only when the ticket is assigned to an agent and the ticket type is not a problem but a question, task, or incident |
| additional_collaborators | array   | no       | Adds collaborators to the request. An email notification is sent to them when the ticket is updated. See [Adding collaborators](/documentation/ticketing/managing-tickets/creating-and-managing-requests#adding-collaborators) |

#### Allowed For

* End users

## Response `200`

Success response

- RequestResponse
  - `request` RequestObject
    - `assignee_id` integer — The id of the assignee if the field is visible to end users
    - `can_be_solved_by_me` boolean — If true, an end user can mark the request as solved. See [Update Request](/api-reference/ticketing/tickets/ticket-requests/#update-request)
    - `collaborator_ids` integer[] — The ids of users currently CC'ed on the ticket
    - `created_at` string, date-time — When this record was created
    - `custom_fields` object[] — Custom fields for the request. See [Setting custom field values](/api-reference/ticketing/tickets/tickets/#setting-custom-field-values) in the Tickets doc
      - `id` integer
      - `value` string
    - `custom_status_id` integer — The custom ticket status id of the ticket
    - `description` string — Read-only first comment on the request. When [creating a request](#create-request), use `comment` to set the description
    - `due_at` string, date-time — When the task is due (only applies if the request is of type "task")
    - `email_cc_ids` integer[] — The ids of users who are currently email CCs on the ticket. See [CCs and followers resources](https://support.zendesk.com/hc/en-us/articles/360020585233) in the Support Help Center
    - `followup_source_id` integer — The id of the original ticket if this request is a follow-up ticket. See [Create Request](#create-request)
    - `group_id` integer — The id of the assigned group if the field is visible to end users
    - `id` integer — Automatically assigned when creating requests
    - `is_public` boolean — Is true if any comments are public, false otherwise
    - `organization_id` integer — The organization of the requester
    - `priority` string — The priority of the request, "low", "normal", "high", "urgent"
    - `recipient` string — The original recipient e-mail address of the request
    - `requester_id` integer — The id of the requester
    - `solved` boolean — Whether or not request is solved (an end user can set this if "can_be_solved_by_me", above, is true for that user)
    - `status` string — The state of the request, "new", "open", "pending", "hold", "solved", "closed"
    - `subject` string, required — The value of the subject field for this request if the subject field is visible to end users; a truncated version of the description otherwise
    - `ticket_form_id` integer — The numeric id of the ticket form associated with this request if the form is visible to end users - only applicable for enterprise accounts
    - `type` string — The type of the request, "question", "incident", "problem", "task"
    - `updated_at` string, date-time — When this record last got updated
    - `url` string — The API url of this request
    - `via` TicketAuditViaObject — Describes how the object was created. See the [Via object reference](/documentation/ticketing/reference-guides/via-object-reference)
      - `channel` string — This tells you how the ticket or event was created. Examples: "web", "mobile", "rule", "system"
      - `source` object — For some channels a source object gives more information about how or why the ticket or event was created

---

[API](https://skmtc.dev/botbrains-io/apis/support-api.md) · [All operations](https://skmtc.dev/botbrains-io/apis/support-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/botbrains-io/support-api/revisions/d53eac07ba68/schema)