---
title: "Change reservation state"
method: POST
path: "/product-reservations/actions/change-reservation-state"
tags: ["Product reservations"]
---

# Change reservation state

`POST /product-reservations/actions/change-reservation-state`

Change a state of existing reservation

## Headers

- `Accept-Language` string

## Request body

- object
  - `product_reservation_id` string, required — The unique ID of the product reservation.
  - `state` 0 | 1 | 2 | 4 | 5 | 6 | 7 | 8, required — A new state of the product reservation. If the reservation is canceled, it won't appear in the reservation list only in the reservation detail. *Possible values: 0 - Canceled / 1 - Entered / 2 - Accepted / 3 - Ready / 4 - Delivered / 5 - In progress / 6 - Not Picked up / 7 - Ordered / 8 - Being solved /*

## Response `204`

No Content

## 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/revisions/329c06dbf8d9/schema)