---
title: "Update a database user"
url: https://docs.corefinity.com/api/reference/database/update-site-database-user
type: endpoint
last_updated: 2026-11-13
feature: database
related:
  - https://docs.corefinity.com/guides/sites/database/database-users.md
  - https://docs.corefinity.com/mcp/tools/corestack_external_db_user_update.md
---
# Update a database user

Changes a user's access and, for an external user, its limits and whether it must connect with TLS: send only
what changes. Sessions that are open keep their old settings until they reconnect. Try-it is off because
making a user read-write needs a typed confirmation.

```http
PATCH /api/corestack/sites/{site}/database/users/{username}
```

- Scope: `write`
- Two-factor: required on your account (all)
- Rate limit: 20 a minute
- Long-running: answers with an operation to poll
- Try it in the console: off. It has not been cleared for the console. 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.
- `username` (string, required): A database user's name, as the database details list it.

## Body

- `confirm_read_write` (string): Sent with `scope: read_write`.
- `max_statement_time` (integer or null): In seconds, from 1 to 86400. Null clears the limit. External users only.
- `max_user_connections` (integer or null): From 1 to 1000. Null clears the limit. External users only.
- `require_tls` (boolean): External users only.
- `scope` (string) One of `read_only`, `read_write`.

## Request

### curl

```bash
curl -X PATCH https://manage.corefinity.com/api/corestack/sites/1042/database/users/reporting_ro \
  -H "Authorization: Bearer $COREFINITY_TOKEN" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "confirm_read_write": "read-write",
    "scope": "read_write"
  }'
```

### PHP

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

$response = Http::withToken(env('COREFINITY_TOKEN'))
    ->acceptJson()
    ->patch('https://manage.corefinity.com/api/corestack/sites/1042/database/users/reporting_ro', [
        'confirm_read_write' => 'read-write',
        'scope' => 'read_write',
    ]);

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

### Node

```javascript
const res = await fetch('https://manage.corefinity.com/api/corestack/sites/1042/database/users/reporting_ro', {
  method: 'PATCH',
  headers: {
    Authorization: `Bearer ${process.env.COREFINITY_TOKEN}`,
    Accept: 'application/json',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    confirm_read_write: 'read-write',
    scope: 'read_write',
  }),
});

// 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.patch(
    "https://manage.corefinity.com/api/corestack/sites/1042/database/users/reporting_ro",
    headers={
        "Authorization": f"Bearer {os.environ['COREFINITY_TOKEN']}",
        "Accept": "application/json",
    },
    json={
        "confirm_read_write": "read-write",
        "scope": "read_write",
    },
)

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

## Responses

### 202 The change is being applied. Follow `operation.id` until it completes.

```json
{
  "operation": {
    "applied_at": "2026-11-03T09:16:40Z",
    "can_retry": false,
    "cluster": {
      "id": 1017,
      "name": "Northwind UK 1"
    },
    "committed_at": null,
    "completed_at": null,
    "created_at": "2026-11-03T09:16:40Z",
    "environment": {
      "env_id": "rs-northwind-harbourandfinch-example-com",
      "hostname": "harbourandfinch-example-com.northwind.cfstack.example.net",
      "id": 1042,
      "name": "Production",
      "role": "production",
      "role_label": "Production",
      "slug": "production"
    },
    "error": null,
    "failure_reason": null,
    "from_version": null,
    "hot": false,
    "id": 5120,
    "install": null,
    "label": "Saved",
    "notes": [],
    "parent_operation_id": null,
    "requested_by": {
      "id": 2012,
      "name": "Daniel Reyes"
    },
    "reset_target": null,
    "result": null,
    "result_state": "none",
    "retried_by_operation_id": null,
    "retries_operation_id": null,
    "retry_requires": null,
    "revealed": null,
    "scope": "site",
    "site": {
      "domain": "harbourandfinch.example.com",
      "id": 1042
    },
    "status": "executing",
    "status_label": "Saving the change",
    "step": "saved",
    "steps": [
      {
        "key": "saved",
        "label": "Saved",
        "state": "current"
      },
      {
        "key": "applied",
        "label": "Applied in the database",
        "state": "todo"
      }
    ],
    "subject": null,
    "summary": "User reporting_ro is now read-write",
    "to_version": null,
    "type": "db_user_change",
    "type_label": "Database users"
  }
}
```

### 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), your company requires two-factor authentication and you have not set it up, or your account has no company that can use Managed Clusters, for example because the company was closed (`company_unavailable` or `company_not_enabled`, whichever the route checks first). For Managed Clusters routes; any other route uses `ForbiddenScopeOrTwoFactor`.

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

### 404 The site id does not exist or is a site you cannot change, the feature is not on for your company (`feature_off`), or no user of that name on this environment can be changed from here (`user_not_found`): an unknown name, the site's own `application` login and the platform's own accounts all answer the same body.

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

### 409 The change was refused because of the site's state. `reason` says why: `deleted`, `provisioning`, `busy` (another change is running), `restore_running`, `removed` 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 wrong (`invalid`, with `field` and `errors`), such as a limit on an internal user or read-write access without `confirm_read_write`; a `confirm_read_write` that is typed and is not `read-write` (`invalid` too, with `detail_reason: confirm_mismatch` beside it); or the user already has these settings (`unchanged`).

```json
{
  "code": "invalid",
  "detail_reason": "confirm_mismatch",
  "errors": {
    "confirm_read_write": [
      "A read-write user can change and delete data. Type read-write to confirm."
    ]
  },
  "field": "confirm_read_write",
  "message": "A read-write user can change and delete data. Type read-write to confirm.",
  "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
}
```

### 503 Corefinity has switched changes to database users off for the moment (`switched_off`). Try again later.

```json
{
  "code": "switched_off",
  "message": "Database users can't be changed just now. Try again later.",
  "reason": "switched_off"
}
```

## 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. |
| 404 | `user_not_found` | There is no such database user on the environment. Read the users again. |
| 409 | `busy` | Another operation is running on the site. Wait for it to finish. |
| 409 | `deleted` | The site, environment or copy has been deleted, or is being deleted. Nothing can be changed on it. Restore a deleted site first if it can still be restored. |
| 409 | `managed_elsewhere` | This site is read-only here. Change it in the control panel that manages it. |
| 409 | `provisioning` | The site is still being created. Try again in a few minutes. |
| 422 | `invalid` | Fix the field named in `field`; `errors` says why. |
| 422 | `unchanged` | Nothing would change. Nothing to do. |
| 429 | `rate_limited` | Wait for the seconds in `Retry-After`. |
| 503 | `switched_off` | Corefinity has switched this action off for the moment. Try again later. |

## The same task elsewhere

- Guide: [Database users](https://docs.corefinity.com/guides/sites/database/database-users.md)
- MCP tool: [`corestack_external_db_user_update`](https://docs.corefinity.com/mcp/tools/corestack_external_db_user_update.md)
