> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/management-api/license/scheduled-updates/create-scheduled-update.md).

# Create Scheduled Update

Schedule one or more changes to a License if requesting manager has access permissions to it.

`scheduled_at` is truncated to the full hour (e.g. `2026-11-01T10:45:00Z` is stored as `2026-11-01T10:00:00Z`). A License can have only one Scheduled Update per hour.

**URL**: `/api/v1/scheduled-updates/`

**Method**: `POST`

## Parameters

* `license` — Integer
  * Required
* `scheduled_at` — Datetime
  * Required
  * Must be at least the next full hour
* `name` — String
  * Maximum length: 255
* `note` — String
* `scheduled_update_data` — List of objects
  * Required
  * Between 1 and 100 items
  * An `action` + `product_feature` + `product_custom_field` combination may appear only once per request, and only once per pending Scheduled Update.
  * Each item:
    * `action` — String
      * Required
      * Choices: `license-update`, `license-reset`, `license-product-feature-update`, `license-product-feature-delete`, `license-custom-field-update`, `license-custom-field-delete`
    * `product_feature` — Integer
      * Required for `license-product-feature-update` and `license-product-feature-delete`
      * Must belong to the same product as the license
    * `product_custom_field` — Integer
      * Required for `license-custom-field-update` and `license-custom-field-delete`
      * Must belong to the same product as the license
    * `update_data` — Object
      * Default: `{}`
      * Content depends on `action`, see below

## `update_data` per action

| Action                           | `update_data`                                                                                                                                                                                                                                                            |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `license-update`                 | Any fields accepted by Update License. Example: `{"validity_period": "2027-11-01", "max_activations": 10}`                                                                                                                                                               |
| `license-reset`                  | Optional reset flags, same as Reset License. Omitted flags use their defaults.                                                                                                                                                                                           |
| `license-product-feature-update` | Any fields accepted by Update License Product Feature. If the product feature is not yet assigned to the license, it is assigned when the update is applied, so `update_data` must then be valid for Create License Product Feature. Example: `{"max_consumption": 100}` |
| `license-product-feature-delete` | `{}`. The product feature must be assigned to the license.                                                                                                                                                                                                               |
| `license-custom-field-update`    | Any fields accepted by Update License Custom Field. If the custom field is not yet set on the license, it is created when the update is applied. Example: `{"value": "EU"}`                                                                                              |
| `license-custom-field-delete`    | `{}`. The custom field must be set on the license.                                                                                                                                                                                                                       |

For `license-reset`, the available flags are:

* `reset_validity_period` — Boolean, default: `true`
* `reset_maintenance_period` — Boolean, default: `true`
* `reset_consumptions` — Boolean, default: `true`
* `reset_metadata` — Boolean, default: `false`
* `reset_product_features` — Boolean, default: `false`
* `reset_custom_fields` — Boolean, default: `false`

`update_data` is validated against the current state of the license when the Scheduled Update is created, and again when it is applied.

## Data example

```json
{
    "license": 1593781720493289,
    "scheduled_at": "2026-11-01T00:00:00Z",
    "name": "Q4 renewal",
    "note": "Extend validity and raise feature limit",
    "scheduled_update_data": [
        {
            "action": "license-update",
            "update_data": {
                "validity_period": "2027-11-01",
                "max_activations": 10
            }
        },
        {
            "action": "license-product-feature-update",
            "product_feature": 173,
            "update_data": {
                "max_consumption": 100
            }
        }
    ]
}
```

## Success Response

**Code**: `201 Created`

**Content examples**:

```json
{
    "id": 412,
    "license": 1593781720493289,
    "created_at": "2026-10-20T09:14:02.118274Z",
    "scheduled_at": "2026-11-01T00:00:00Z",
    "status": "pending",
    "applied_at": null,
    "cancelled_at": null,
    "failed_at": null,
    "name": "Q4 renewal",
    "note": "Extend validity and raise feature limit",
    "scheduled_update_data": [
        {
            "id": 981,
            "action": "license-update",
            "product_feature": null,
            "product_custom_field": null,
            "update_data": {
                "validity_period": "2027-11-01",
                "max_activations": 10
            },
            "error_message": null
        },
        {
            "id": 982,
            "action": "license-product-feature-update",
            "product_feature": 173,
            "product_custom_field": null,
            "update_data": {
                "max_consumption": 100
            },
            "error_message": null
        }
    ]
}
```

## Error Responses

**Code:** `400 Bad Request`

```json
{
    "scheduled_at": [
        "Scheduled time must be at least 2026-10-20 10:00:00 (next full hour)."
    ]
}
```

```json
{
    "scheduled_at": [
        "A pending scheduled update with this action already exists for this license at this time."
    ]
}
```

```json
{
    "scheduled_at": [
        "A scheduled update already exists for this license at this time."
    ]
}
```

Returned when a non-pending (applied, cancelled or failed) Scheduled Update already exists for the license at that hour.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.licensespring.com/management-api/license/scheduled-updates/create-scheduled-update.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
