---
title: "Restore an Nginx revision"
url: https://docs.corefinity.com/api/reference/site-settings/restore-site-nginx-revision
type: endpoint
last_updated: 2026-11-13
feature: nginx-rules
related:
  - https://docs.corefinity.com/guides/sites/site-settings/web-server-rules.md
  - https://docs.corefinity.com/mcp/tools/corestack_nginx_rules_revert.md
---
# Restore an Nginx revision

Restores a revision as a new revision: a hook the old revision did not have is cleared. The restore is checked, tested and applied like any save, and answers the same.

```http
POST /api/corestack/sites/{site}/nginx-rules/revisions/{revision}/revert
```

- Scope: `write`
- Two-factor: required on your account (all)
- Rate limit: 60 a minute; 20 a minute for each environment
- Long-running: answers with an operation to poll
- Try it in the console: off. It overwrites data that cannot be brought back. Copy the request and run it yourself when you are sure.

## Path parameters

- `site` (integer, required): The id of a site row. A website's production site and each of its environments has its own id. Digits only.
- `revision` (integer, required): The id of a revision of this site, from the list's `id`.

## Body

- `apply` (string): When the change applies, if it needs a one-time update of the site's runtime first. Most changes apply at once whatever is sent. When a change that needs a maintenance window is applied. `now` applies it at once. `tonight` queues it for the site's next window. `window` means the same as `tonight`. An endpoint that takes `window` only while maintenance windows are on for your company says so, and refuses it `422` on `apply` otherwise. One of `now`, `tonight`, `window`. Defaults to `now`.
- `note` (string or null): Why, shown in the history. "Restored revision" and its number when left out.
- `test_id` (integer): A passed test run of the same content, from a check, so it is not run again.
- `version` (integer, required): The `version` from the last read.

## Request

### curl

```bash
curl -X POST https://manage.corefinity.com/api/corestack/sites/1042/nginx-rules/revisions/1/revert \
  -H "Authorization: Bearer $COREFINITY_TOKEN" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "note": "Back to the rules of 28 September",
    "version": 2
  }'
```

### PHP

```php
use Illuminate\Support\Facades\Http;

$response = Http::withToken(env('COREFINITY_TOKEN'))
    ->acceptJson()
    ->post('https://manage.corefinity.com/api/corestack/sites/1042/nginx-rules/revisions/1/revert', [
        'note' => 'Back to the rules of 28 September',
        'version' => 2,
    ]);

$data = $response->json();
```

### Node

```javascript
const res = await fetch('https://manage.corefinity.com/api/corestack/sites/1042/nginx-rules/revisions/1/revert', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.COREFINITY_TOKEN}`,
    Accept: 'application/json',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    note: 'Back to the rules of 28 September',
    version: 2,
  }),
});

// An answer with no body (204) has nothing to parse.
const text = await res.text();
const data = text && JSON.parse(text);
```

### Python

```python
import os
import requests

res = requests.post(
    "https://manage.corefinity.com/api/corestack/sites/1042/nginx-rules/revisions/1/revert",
    headers={
        "Authorization": f"Bearer {os.environ['COREFINITY_TOKEN']}",
        "Accept": "application/json",
    },
    json={
        "note": "Back to the rules of 28 September",
        "version": 2,
    },
)

data = res.json() if res.content else None
```

## Responses

### 200 The revision holds what the site already has. Nothing was started.

```json
{
  "operation": null,
  "revision": null
}
```

### 201 The restore was saved as a new revision. Follow `operation`.

```json
{
  "item_id": 77,
  "operation": null,
  "queued": true,
  "revision": null,
  "window_date": "2026-11-07"
}
```

### 401 No token, or a token that is not valid.

```json
{
  "message": "Unauthenticated."
}
```

### 403 The token lacks the scope (`scope_required`, with the `scope` to use), or your company requires two-factor authentication and you have not set it up. For routes outside Managed Clusters.

```json
{
  "code": "company_unavailable",
  "message": "Your company is unavailable.",
  "reason": "company_unavailable"
}
```

### 404 The id does not exist or is something you cannot see, or the feature is not on for your company (`feature_off`).

```json
{
  "code": "feature_off",
  "message": "Not found.",
  "reason": "feature_off"
}
```

### 409 The request was refused because of the site's state. `reason` says why: `stale` (the rules changed since your read: read them again and send the new `version`), `busy` or `change_pending` (another change is running or waiting), `restore_running`, `command_running` or `deployment_running` (a restore, a command or a deployment is running on the site), `conflict` (another change to the platform landed first: send the request again), `cluster_paused`, `cluster_not_ready` or `cluster_deleting` (the site's cluster cannot take changes at the moment), or `managed_elsewhere`.

```json
{
  "code": "busy",
  "message": "Another change to this site is in progress. Wait for it to finish.",
  "reason": "busy"
}
```

### 422 A field is missing or wrong (`invalid`, with `field` and `errors`), or the change was refused for a reason of its own: `nginx_invalid` (the rules break the policy; `diagnostics` lists each problem), `nginx_test_failed` (the rules failed the test on the site's own Nginx; `diagnostics`), `hook_unavailable` (the site cannot use that hook yet), `nginx_rules_locked` (Corefinity manages the site's Nginx rules), or `feature_off` when `apply` asks for a window and changes cannot wait for one at the moment.

```json
{
  "code": "feature_off",
  "message": "Queuing changes for the maintenance window is switched off at the moment",
  "reason": "feature_off"
}
```

### 429 Too many requests (`rate_limited`): the API's general limit, or the 20 saves a minute this environment takes from the API, the Control Panel and AI assistants together. Wait for `Retry-After`, which `retry_after_seconds` repeats.

```json
{
  "code": "rate_limited",
  "message": "Too many attempts on this environment. Try again shortly.",
  "reason": "rate_limited",
  "retry_after_seconds": 60
}
```

### 500 The platform did not answer while the site's files were being read for the change, or the Control Panel may not write this site's files. Nothing was changed. When the platform is at fault, send the request again in a minute. The answer is a sentence only, with no `reason`.

```json
{
  "message": "Server Error"
}
```

### 502 The platform did not save the change. Nothing was changed. Send the request again in a minute. The answer is a sentence only, with no `reason`.

```json
{
  "message": "The change could not be saved. Contact support."
}
```

### 503 The rules sent are the saved ones, a change made outside the Control Panel is waiting, and the site's configuration cannot be read at the moment to put the saved rules back (`upstream_unavailable`). Try again in a few minutes.

```json
{
  "code": "upstream_unavailable",
  "message": "This environment's configuration repository can't be read right now. Try again in a few minutes.",
  "reason": "upstream_unavailable"
}
```

## If it is refused

| Status | Reason | What to do |
|---|---|---|
| 401 |  | Send a valid token as `Authorization: Bearer <token>`. |
| 403 | `company_unavailable` | Your company is unavailable. |
| 403 | `scope_required` | Use a token with the scope named in `scope`. |
| 403 | `two_factor_required` | Turn on two-factor on your account, then send again. |
| 404 | `feature_off` | This feature is not on for your organisation yet. |
| 409 | `busy` | Another operation is running on the site. Wait for it to finish. |
| 409 | `conflict` | The action conflicts with the object's present state. Read the message. |
| 409 | `managed_elsewhere` | This site is read-only here. Change it in the control panel that manages it. |
| 409 | `restore_running` | A restore is running on the site. Wait for it to finish, then try again. |
| 409 | `stale` | What you read has changed since you read it. Read it again, then send the change with its new version or quote. |
| 422 | `feature_off` | This feature is not on for your organisation yet. |
| 422 | `invalid` | Fix the field named in `field`; `errors` says why. |
| 422 | `nginx_invalid` | These nginx rules cannot be saved: fix the errors shown. |
| 422 | `nginx_rules_locked` | Corefinity has locked this environment's nginx rules. Contact support to change them. |
| 429 | `rate_limited` | Wait for the seconds in `Retry-After`. |
| 500 |  | Read the message; it says what happened. |
| 502 |  | Read the message; it says what happened. |
| 503 | `upstream_unavailable` | A service the action depends on did not answer. Try again later. |

## The same task elsewhere

- Guide: [Web server rules](https://docs.corefinity.com/guides/sites/site-settings/web-server-rules.md)
- MCP tool: [`corestack_nginx_rules_revert`](https://docs.corefinity.com/mcp/tools/corestack_nginx_rules_revert.md)
