---
title: "Get one Nginx revision"
url: https://docs.corefinity.com/api/reference/site-settings/get-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_revision_get.md
---
# Get one Nginx revision

Answers one revision with the text of its hooks and a unified diff of each hook against the current revision, or against another one.

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

- Scope: `read`
- Two-factor: required on your account (all)
- Rate limit: 120 a minute
- Try it in the console: on

## 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`.

## Query parameters

- `against` (string): The id of the revision to compare with, or `current` (the default).

## Request

### curl

```bash
curl https://manage.corefinity.com/api/corestack/sites/1042/nginx-rules/revisions/1 \
  -H "Authorization: Bearer $COREFINITY_TOKEN" \
  -H "Accept: application/json"
```

### PHP

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

$response = Http::withToken(env('COREFINITY_TOKEN'))
    ->acceptJson()
    ->get('https://manage.corefinity.com/api/corestack/sites/1042/nginx-rules/revisions/1');

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

### Node

```javascript
const res = await fetch('https://manage.corefinity.com/api/corestack/sites/1042/nginx-rules/revisions/1', {
  method: 'GET',
  headers: {
    Authorization: `Bearer ${process.env.COREFINITY_TOKEN}`,
    Accept: 'application/json',
  },
});

// 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.get(
    "https://manage.corefinity.com/api/corestack/sites/1042/nginx-rules/revisions/1",
    headers={
        "Authorization": f"Bearer {os.environ['COREFINITY_TOKEN']}",
        "Accept": "application/json",
    },
)

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

## Responses

### 200 The revision and its differences.

```json
{
  "against": {
    "current": true,
    "id": 317
  },
  "diff": {
    "headers": null,
    "http": null,
    "php": null,
    "server": "--- revision 2\n+++ revision 1\n@@ -1,3 +1,3 @@\n-location = /older {\n-    return 410;\n+location = /old {\n+    return 404;\n }\n"
  },
  "revision": {
    "author": {
      "client": null,
      "kind": "user",
      "name": "Eleanor Finch"
    },
    "content": {
      "headers": null,
      "http": null,
      "php": null,
      "server": "location = /old {\n    return 404;\n}\n"
    },
    "created_at": "2026-11-01T10:02:11Z",
    "errors_since": null,
    "hooks_changed": [
      "server"
    ],
    "id": 316,
    "note": "First rules",
    "number": 1,
    "origin": "editor",
    "status": "applied",
    "status_reason": null
  }
}
```

### 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"
}
```

### 422 `against` is not `current` or a revision of this site (`invalid`).

```json
{
  "code": "invalid",
  "errors": {
    "against": [
      "against is current or a revision of this environment."
    ]
  },
  "field": "against",
  "message": "against is current or a revision of this environment.",
  "reason": "invalid"
}
```

### 429 Too many requests (`rate_limited`). Wait for the number of seconds in `Retry-After`, which `retry_after_seconds` repeats.

```json
{
  "code": "rate_limited",
  "message": "Too many requests. Try again in 60 seconds.",
  "reason": "rate_limited",
  "retry_after_seconds": 60
}
```

## 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. |
| 422 | `invalid` | Fix the field named in `field`; `errors` says why. |
| 429 | `rate_limited` | Wait for the seconds in `Retry-After`. |

## 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_revision_get`](https://docs.corefinity.com/mcp/tools/corestack_nginx_rules_revision_get.md)
