# Update a cycle on a subscription

Overrides the charge amount for a single cycle without touching the subscription's recurring schedule or default value. Only `RENEWABLE` cycles in `PENDING` status can be patched — anything else (one-off charges, already-processed cycles, deleted cycles) returns `409 Conflict`.
**Required scope:** <code style="background:#e8f0fe;color:#1a73e8;padding:2px 8px;border-radius:12px;font-size:0.85em">subscription:update</code>

Endpoint: PATCH /subscription/{id}/cycle/{cycle_id}
Version: 2.0
Security: accountId, apiKey

## Path parameters:

  - `id` (string, required)
    UUID of the subscription the cycle belongs to.

  - `cycle_id` (string, required)
    UUID of the cycle to update.

## Request fields (application/json):

  - `value` (number, required)
    New amount for the cycle, in euros. Must have at most two decimal places.
    Example: 99.99

## Response 200 fields (application/json):

  - `status` (string, required)
    Example: ok

  - `message` (array, required)
    Example: ["Your request was successfully updated"]

  - `id` (string, required)
    The UUID of the updated cycle (same as the `cycle_id` path parameter).
    Example: 550e8400-e29b-41d4-a716-446655440000

## Response 400 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 401 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 403 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 404 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 409 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 412 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 429 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 500 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.