# Manage customer servers in the staff console

> Find any customer server, check its health and act on it from the staff console, within your role's limits.

Source: https://docs.coritan.com/organizations/staff-console/servers/

`/staff/servers` in the staff console lists every server your customers hold. Each server's page, at `/staff/servers/{uuid}`, lets your team do most of what the customer can do in their own panel: power, the live console, files, ports, databases, snapshots, schedules, software, startup and subusers. Staff also see what the customer cannot: the node the server runs on, its real address and its last install error. Use these pages to answer a support question, fix an install or act on abuse.

## Before you begin

Readonly and Tier 1 members cannot open these pages. On them each role can do everything the roles below it can, and the tasks need:

| Task | Lowest role | Step-up |
| --- | --- | --- |
| Find servers, and read a server's details, resource use and sleep state | Tier 2 support | No |
| Watch the live console, and read and download files in `logs/` and `crash-reports/` | Tier 2 support | No |
| Everything else on a server: power, commands, files, ports, databases, snapshots, schedules, software, settings and subusers | Tier 3 support | No |
| Read a database's password | Tier 3 support | Yes |
| Suspend many servers at once, or lift their suspension | Tier 3 support | No |
| Delete a schedule | Admin | No |
| Change a server's runtime, startup command or variables | Admin | Yes |
| Restore or delete a snapshot or backup, or delete a database | Admin | Yes |
| Terminate many servers, ban their owners, or suspend with a deletion date | Admin | Yes |

A *step-up* is a fresh password or authenticator code, which lasts 10 minutes; [Sign in to the staff console](/organizations/staff-console/sign-in/#confirm-it-is-you) explains it. Staff actions have the same limits as the customer's, counted for each member on each server. The sections below give them.

## Find a server

1. Open `/staff/servers`.
2. Search by the server's name, hostname or UUID, the owner's email, or the IP address. A `*` matches any text, so `*@example.com` finds the servers of every owner at that domain.
3. Choose a status to narrow the list:
   - `running`, `offline`, `starting` and `stopping` say what the node last saw the server doing, and `unknown` means the node has not reported on it yet.
   - `installing`, `install_failed`, `suspended` and `transferring` hold servers that cannot run in that state.
   - `attention` holds failed installs, servers moving between nodes, and installs that have run for more than 3 minutes.
   - `watch` holds free servers that have a port beyond the primary, or have run for 7 days without a stop. Neither proves abuse, so treat the list as a place to start checking.
   - `free` holds every free server.
4. To narrow further, filter by node, owner, software, creation date, ports beyond the primary, days of uptime or average CPU, and keep only paying or only free customers.

Without a sort, failed installs and transfers come first, then the newest. You can sort by any column, players online and uptime included. Each row shows the server's status, players online, uptime, address and owner, and its CPU, memory and disk use against its limits. A server our abuse review has locked is marked as locked.

## Check a server's health

Open the server from the list. Its page names the owner and the order, and shows:

- the live console and the server's resource use;
- the node and location it runs on, and its real address, even on a free server whose customers see only the hosted address;
- its plan limits, its runtime and its last install error.

Tier 2 sees the console and the logs only. To read the rest of a server's files, ask the customer for access from their support conversation, as [Answer customer conversations](/organizations/staff-console/support-inbox/) explains.

A free server sleeps when nobody plays on it, as [How free servers work](/managed-containers/free-servers/) explains, and its page shows the phase it is in: `awake`, `starting`, `queued` or `asleep`.

## Start, stop and use the console

- Start, restart or stop the server, or kill it when it will not stop. Each member may send 24 power actions a minute to one server.
- Wake a sleeping free server. A paid server does not sleep, so start it instead.
- When a free server stays stuck in the start queue, kick the queue. We check the server against its node and, if it is still down, start it ahead of the queue. The console offers this to admins only, and Tier 3 support can also do it through the API.
- Type a command into the live console, or send one of up to 1,000 characters. We record each command in the audit log, up to its first 200 characters. Each member may send 60 commands a minute to one server.

Tier 2 can watch the console but cannot type in it.

## Work with files

Tier 2 may list, read and download files inside `logs/` and `crash-reports/`, where a server writes down its problems. Tier 3 has the customer's whole file manager: edit files, make folders, upload files of up to 100 MB each, rename, copy and delete, change permissions, compress and extract archives, and download a file from a URL onto the server. Compressing, extracting and downloading from a URL each allow 24 a minute for each member on one server.

We record every change in the audit log with the paths it touched.

## Add a port for a port request

Your organization can make free customers ask for extra ports instead of adding them, with the port requests switch described in [Manage the staff team and console settings](/organizations/staff-console/team-and-settings/). Paid servers are never affected. Each request arrives in the support inbox as a conversation tagged `port-request` and `free`, with the subject `Extra port for` and the server's name, and the customer's reason in the first message.

1. Open the conversation in `/staff/inbox` and read what the port is for.
2. Add the port with the conversation's server action. The console notes the conversation's number on the port and tells you which port it added. You can also open the server and add a port from its ports.
3. Reply to the customer with the port number, and close the conversation.

We pick a free port from the node's shared range, 10000–40000, unless you choose one. A server may hold 5 shared ports including its primary, unless its plan sets another number, and the ports we manage for Bedrock players do not count. On a server with a Floating IP you can instead open any port from 1024 to 65535 on that address, up to 16 of them.

Your team can also:

- Make a port the primary one, which players connect to. We move the server onto it and restart the server if it is running.
- Publish a port on the game's default port, 25565 or 19132, of the server's Floating IP.
- Release a port. The primary port, a port we manage, and the last shared port of a server with a Floating IP cannot be released.

[Manage server ports](/managed-containers/ports/) explains ports as the customer sees them.

## Fix a failed install

1. Choose `attention` or `install_failed` on `/staff/servers`, and open the server.
2. Read the install log: the last 400 lines the install script wrote, and the output we recorded while it ran.
3. Heal the install. We read the server's disk first: when the files are in place, we mark the server running and reinstall nothing, and otherwise we run the install again. To run the install again without that check, retry it instead, which works only on a server that is `install_failed` or `installing`.

To heal every broken install at once, use the heal action on `/staff/servers`. It takes up to 25 servers, oldest first: failed installs, and installs that nothing has moved for 45 seconds.

Each member may reinstall, retry or heal one server 8 times in 10 minutes. A reinstall of a working server wipes every file on it, so use it only when the customer wants to start again.

## Save and restore snapshots

Tier 3 lists the server's snapshots, or every snapshot its owner holds with whether each can be restored onto this server. Tier 3 can also check whether a new snapshot fits, take one, download one, and lock or unlock one. An admin who has stepped up can restore a snapshot onto the server, which replaces its files, or delete one.

Snapshots count against the owner's snapshot storage, as [How snapshot storage works](/snapshots/storage-allowance/) explains. Servers made before snapshots may still have backups: your team can list, lock, restore and delete them with the same roles, but cannot take a new one.

## Manage databases

Tier 3 lists a server's databases, creates one, sets a new password for one, and retries one that failed to create. Reading a password needs a step-up. Deleting a database needs an admin who has stepped up, because nothing brings it back. For each member on one server, creating allows 24 a minute and setting a new password 16 a minute.

## Untangle a schedule

Tier 3 reads a server's schedules and their recent runs, runs a schedule now, and pauses or resumes one that is hurting the server. An admin can delete a schedule. Creating and changing schedules stays with the customer.

## Change software, startup and settings

- Software: Tier 3 sees what the server runs and what it can change to, changes it, and cancels or retries a stuck add-on install. A change that wipes the server needs its name typed to confirm. Each member may change one server's software 8 times in 10 minutes.
- Startup: Tier 3 reads how the server starts. An admin who has stepped up can move it to another runtime of the same kind, such as Java 17 to Java 21, set or reset its startup command, and set or remove environment variables. The change applies at the next start, and we do not restart the server.
- Settings: Tier 3 renames the server, turns world optimization on or off, changes the subdomain of its join address, and sets the startup variables its game allows. When the server has a custom domain, we email the customer the new target for their DNS record.

## Manage who else can reach a server

Tier 3 lists the server's subusers, trims one's permissions, or removes one. We email the person you removed. Removing also cancels an invite that has not been accepted. Adding people stays with the owner, as [Share a server with other users](/managed-containers/users/) explains.

## Act on many servers at once

Select up to 100 servers on `/staff/servers`, give a reason of 3–500 characters, and choose an action:

- Suspend stops each server as an unpaid invoice would, and keeps its files. An admin who has stepped up can add a deletion date 1–90 days away, when we delete the server.
- Unsuspend lifts the suspension, and calls off a deletion date your team set.
- Terminate, for an admin who has stepped up, ends each order now with no credit and keeps a snapshot. We email the customer only when you choose to.
- Ban, for an admin who has stepped up, bans each owner, ends their sessions and ends every order they have, including servers you did not select.

Unless you turn it off, each customer gets one conversation in your inbox's `abuse` department, assigned to you. The customer reads a notice that names the servers without saying how you found them, and your reason stays in an internal note. Lifting a suspension opens no conversation. We skip servers that are outside your organization or already ending, and list each with its reason. Each member may run 12 of these an hour.

## Result

Each change shows on the server at once, and the customer sees it in their own panel. The [audit log](/organizations/audit-log/) records every action with the member who took it and the server's UUID.

## Troubleshooting

`Tier 2 support access required`
: Readonly and Tier 1 members cannot open servers. Ask an admin for a Tier 2 role or higher.

`Support access required`
: The action needs Tier 3 support or a higher role.

`Server is not in this organization`
: The server belongs to another organization, or its order has been terminated. A UUID that matches no server answers `404 Server not found`.

`Tier 2 reads a server's logs/ and crash-reports/; ask the customer for access to see the rest`
: Below Tier 3 you can read only those two folders. Ask the customer for access from their conversation.

`423` with `reason` set to `server_locked`
: Our abuse review has locked the server. The customer's conversation about the lock is in your inbox's `abuse` department. Only we can lift the lock, so escalate that conversation to us if you think it is a mistake.

`409` with `reason` set to `world_optimization_running`
: We are removing unused chunks and the server cannot start until that ends. Try again after `retry_after_seconds`.

`This server does not sleep; use the power action to start it.`
: The server is on a paid plan. Start it instead of waking it.

`Not a free-tier server; use a power action`
: Only a free server has a start queue. Start the server instead.

`Server is running, not install_failed or installing`
: A retry only reruns a failed or stuck install. To start a working server again from nothing, reinstall it, which wipes its files.

`Allocation limit reached (5). Cannot add more ports to this server.`
: The server holds every shared port its plan allows. Release one, or open the port on the server's Floating IP.

`Port must be between 10000 and 40000`
: Choose a port in the shared range, or leave the port out and we pick one.

`Port 25565 is reserved on the node main IP (gameproxy / platform services)`
: We keep that port for our own services on the node. Choose another, or leave the port out.

`Port 20145 is already in use on this node`
: Another server holds that port. Choose another, or leave the port out.

`Attach a floating IP first; there is no dedicated address to open a port on`
: The server has no Floating IP. Open the port in the shared range instead.

`Cannot release the primary allocation`
: Make another port primary first.

`Keep at least one shared node port: it is what this server falls back to if the floating IP is detached.`
: A server with a Floating IP keeps one port in the shared range.

`java-17 is not a nodejs runtime; changing the runtime family is a software change, which reinstalls`
: A runtime moves only within its kind. Change the server's software instead.

`No database host on this server's node`
: We have not set up databases on the node this server runs on. Contact our [support](/support/).

`402` with `reason` set to `over_allowance`
: The snapshot does not fit the owner's snapshot storage. Delete an old snapshot, or ask the customer to add storage.

`410` with `reason` set to `replaced_by_snapshots`
: Snapshots have replaced backups. Take a snapshot instead.

`Ending servers or accounts needs an org admin; support can suspend without a deletion date`
: Terminate, ban and a suspension with a deletion date need an admin. Suspend without a date, or ask an admin.

`429` with `error` set to `rate_limited`
: You reached the limit for that action on this server. Try again after `retry_after_seconds`.

## Related

- [Answer customer conversations](/organizations/staff-console/support-inbox/), where port requests arrive and you ask for access to a server
- [Let customers run their servers](/organizations/storefront/portal-servers/), the same servers from the customer's side
- [Handle billing in the staff console](/organizations/staff-console/billing/), to suspend, cancel or retry the order behind a server
- [Look after customers in the staff console](/organizations/staff-console/customers/#see-the-storefront-as-the-customer), to open the customer's own panel

## With the API

These routes live under `https://api.coritan.com/api/v1/orgs/{org_slug}/staff/servers/`, and take a console session or a member's access token as [The staff console](/organizations/staff-console/#with-the-api) explains. A step-up needs a console session. [Servers in the staff console](/api/reference/organizations/org-staff-containers/staff/) lists every route but one: the reference lists `PATCH /staff/servers/{uuid}/settings` with [the brand settings routes](/api/reference/organizations/organizations-members/staff/#op-patch-api-v1-orgs-org-slug-staff-servers-uuid-settings).

### List the fleet

```bash
curl "https://api.coritan.com/api/v1/orgs/acme/staff/servers?status=watch&owner=*@example.com&sort=uptime&limit=50" \
  -H "Authorization: Bearer $STAFF_TOKEN"
```

The answer is a list of servers, each with `uuid`, `name`, `hostname`, `status`, `power`, `customer`, `node_name`, `address`, `usage`, `uptime_seconds`, `join_address`, `players_online`, `extra_ports`, `is_free`, `locked` and `install`. The list takes:

- `q`, up to 200 characters, matched against the name, hostname, UUID, owner's email and IP address. A `*` is a wildcard here and in `name` and `owner`.
- `status`, one of the words in [Find a server](#find-a-server), or `all`.
- `node_id`, `customer_id`, or `customer_ids` with up to 100 comma-separated IDs.
- `audience`: `paid`, `free` or `all`.
- `name` (server name or hostname), `owner` (email, name or company) and `software` (runtime name), each up to 200 characters; `created_after` and `created_before`, whole days that both count; `min_extra_ports` 0–64; and `up_days_min`.
- `cpu_min`, as a percentage of one core, or `cpu_of_limit_min`, as a percentage of the server's own limit, averaged over `cpu_window`: `15m` or `1h` (the default).
- `sort`: `created`, `updated`, `name`, `status`, `players`, `join_address`, `ip`, `port`, `node`, `owner`, `template`, `cpu`, `memory`, `disk`, `cpu_limit`, `memory_limit`, `disk_limit`, `uptime` or `id`. `dir` is `asc` or `desc`; names sort ascending and figures descending unless you say otherwise.
- `limit` 1–200 (50 by default) and `offset`.

An unknown `sort` answers `400` with the words it takes. `GET /staff/servers/stats` counts the servers in each status, with `attention`, `watch`, `slow_installs` and each node's `total` and `install_failed`. `GET /staff/servers/live?uuids=` takes up to 100 comma-separated UUIDs and answers each one's live `state`, `usage`, `players_online` and `join_address`. It leaves out any UUID outside your organization.

### Read one server

`GET /staff/servers/{uuid}` answers the server as the customer sees it, plus `customer_id`, `customer_email`, `customer_name`, `org_service_id`, `org_service_status` and `infrastructure`: the `node_name`, `location`, real `address`, limits, `docker_image`, `template_name`, `sleep_policy`, `allocation_limit`, `database_limit`, `installed_at`, `last_error` and `last_error_at`. `GET /resources` answers live resource use, and `GET /sleep` answers the `sleep` state and the plan's `entitlements`.

Tier 2 reads logs with the file routes:

```bash
curl "https://api.coritan.com/api/v1/orgs/acme/staff/servers/$SERVER_UUID/files/contents?path=/logs/latest.log" \
  -H "Authorization: Bearer $STAFF_TOKEN"
```

`GET /files/list?directory=/crash-reports` lists a folder, and `GET /files/download?path=` streams one file. `GET /websocket` answers a `token` and the `socket` address of the live console.

### Power and commands

```bash
curl -X POST https://api.coritan.com/api/v1/orgs/acme/staff/servers/$SERVER_UUID/power \
  -H "Authorization: Bearer $STAFF_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"signal": "restart"}'
```

```json
{"message": "Power action 'restart' sent"}
```

`signal` is `start`, `stop`, `restart` or `kill`. `POST /command` takes `{"command": "say Back in five minutes"}`, 1–1000 characters. `POST /wake` wakes a sleeping free server and answers its `sleep` state, and `POST /wake-queue/kick` starts one that is stuck in the queue. `POST /reinstall` reinstalls the server.

### Add a port

```bash
curl -X POST https://api.coritan.com/api/v1/orgs/acme/staff/servers/$SERVER_UUID/allocations \
  -H "Authorization: Bearer $STAFF_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"notes": "port request #1042"}'
```

It answers `201` with the new port's `id`, `ip`, `port`, `notes` and `is_primary`. Send `port` to choose the port, and `on_dedicated_ip: true` to open it on the server's Floating IP. `GET /allocations` answers the server's ports as `items`, with `allocation_limit` and `allocation_used`, and `GET /allocations/available-ports?limit=50` lists up to 200 free ones. `POST /allocations/{allocation_id}/primary` makes a port primary, `POST /allocations/{allocation_id}/publish-port` takes `{"port": 25565}` or `{"port": null}` to clear it, and `DELETE /allocations/{allocation_id}` answers `{"message": "Allocation released"}`.

### Fix installs

`GET /install-log` answers the `status`, `last_error`, the install script's `script_log` and our `recorded_output`, each up to 400 lines. `POST /heal-install` takes `{"start_after": true}` to start the server once it is healed, and answers the `action` we took: `marked_running`, `reinstall_started` or `reinstall_failed`. `POST /retry-install` answers `409` for a server that is not `install_failed` or `installing`. `POST /staff/servers/heal-installs?limit=25` heals up to 25 broken installs and answers how many were `healed`, `reinstalled` and `failed`.

### Snapshots, databases, schedules and startup

| Route | Lowest role |
| --- | --- |
| `GET /snapshots?scope=this` or `scope=account`, `GET /snapshots/estimate`, `POST /snapshots`, `GET /snapshots/{snapshot_uuid}/download`, `POST /snapshots/{snapshot_uuid}/lock` | Tier 3 support |
| `POST /snapshots/{snapshot_uuid}/restore`, `DELETE /snapshots/{snapshot_uuid}`, and the same two for `/backups/{backup_uuid}` | Admin, stepped up |
| `GET` and `POST /databases`, `POST /databases/{database_id}/rotate-password` and `/retry` | Tier 3 support |
| `GET /databases/{database_id}/credentials` | Tier 3 support, stepped up |
| `DELETE /databases/{database_id}` | Admin, stepped up |
| `GET /schedules`, `GET /schedules/{schedule_uuid}` and `/runs`, `POST /schedules/{schedule_uuid}/execute`, `POST /schedules/{schedule_uuid}/toggle` with `{"is_active": false}` | Tier 3 support |
| `DELETE /schedules/{schedule_uuid}` | Admin |
| `GET /startup` | Tier 3 support |
| `PATCH /startup` | Admin, stepped up |

`POST /snapshots` takes an optional `name` of up to 191 characters. A restore replaces the server's files; send `{"truncate": false}` to keep files the snapshot does not hold. `PATCH /startup` takes `runtime_template_slug`, `startup_command` (one line, up to 4,000 characters) or `reset_startup_command: true`, `variables` to set and `remove_variables`. Variable names are capital letters, digits and underscores, and values are one line of up to 1,024 characters.

### Software, settings and subusers

`GET /software/context` says what the server runs, `GET /software/catalog` lists what it can change to, and `POST /software/change` takes `target_key`, `version` and `mode`: `keep`, or `wipe` with `confirm_server_name`. `PATCH /settings` takes `name` and `world_optimization_enabled`, `PATCH /subdomain` takes a `subdomain` of 1–28 characters, and `PATCH /startup-variables` takes the `variables` the game allows. `GET /users` lists subusers, `PUT /users/{subuser_id}` takes their `permissions`, which `GET /permissions` lists, and `DELETE /users/{subuser_id}` removes one.

### Act on many servers

```bash
curl -X POST https://api.coritan.com/api/v1/orgs/acme/staff/servers/bulk \
  -H "Authorization: Bearer $STAFF_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"uuids": ["3f6c2a9e-8b1d-4c57-9e02-5d7a41b8c613", "b72d0e41-5a9c-4f3b-8e61-0c4d2f7a9b35"], "action": "suspend", "reason": "Crypto mining on free servers", "delete_after_days": 14}'
```

`action` is `suspend`, `unsuspend`, `terminate` or `ban`. `delete_after_days` (1–90) applies to a suspension, `open_ticket` defaults to `true`, and `notify_customer` (default `false`) sends the cancellation email on a termination. The answer lists the UUIDs `applied`, the ones `skipped` with a `reason`, each customer with their `servers` and `ticket_id`, and the `termination_date`.

## API

- `GET /api/v1/orgs/{org_slug}/staff/servers`: Staff fleet (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers)
- `POST /api/v1/orgs/{org_slug}/staff/servers/bulk`: Suspend, unsuspend, terminate, or ban the owners of, a selection of this brand's servers (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-bulk)
- `POST /api/v1/orgs/{org_slug}/staff/servers/heal-installs`: Staff heal installs (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-heal-installs)
- `GET /api/v1/orgs/{org_slug}/staff/servers/live`: Live state, usage and players for the brand's servers on one screen (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-live)
- `GET /api/v1/orgs/{org_slug}/staff/servers/stats`: How many servers sit in each bucket, and the nodes they sit on (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-stats)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}`: Staff server detail (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/allocations`: Staff list allocations (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-allocations)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/allocations`: Staff create allocation (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-allocations)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/allocations/available-ports`: Staff available ports (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-allocations-available-ports)
- `DELETE /api/v1/orgs/{org_slug}/staff/servers/{uuid}/allocations/{allocation_id}`: Staff delete allocation (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-delete-api-v1-orgs-org-slug-staff-servers-uuid-allocations-allocation-id)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/allocations/{allocation_id}/primary`: Staff set primary allocation (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-allocations-allocation-id-primary)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/allocations/{allocation_id}/publish-port`: Publish a port on 25565 / 19132 of the customer's floating IP, or clear it (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-allocations-allocation-id-publish-p)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/backups`: Staff list backups (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-backups)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/backups`: Staff create backup (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-backups)
- `DELETE /api/v1/orgs/{org_slug}/staff/servers/{uuid}/backups/{backup_uuid}`: Staff delete backup (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-delete-api-v1-orgs-org-slug-staff-servers-uuid-backups-backup-uuid)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/backups/{backup_uuid}/lock`: Staff toggle backup lock (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-backups-backup-uuid-lock)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/backups/{backup_uuid}/restore`: Staff restore backup (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-backups-backup-uuid-restore)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/command`: Staff command (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-command)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/databases`: Staff list databases (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-databases)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/databases`: Staff create database (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-databases)
- `DELETE /api/v1/orgs/{org_slug}/staff/servers/{uuid}/databases/{database_id}`: Staff delete database (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-delete-api-v1-orgs-org-slug-staff-servers-uuid-databases-database-id)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/databases/{database_id}/credentials`: Staff database credentials (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-databases-database-id-credentials)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/databases/{database_id}/retry`: Staff retry database (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-databases-database-id-retry)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/databases/{database_id}/rotate-password`: Staff rotate database password (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-databases-database-id-rotate-passwo)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/files/chmod`: Staff chmod files (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-files-chmod)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/files/compress`: Staff compress files (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-files-compress)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/files/contents`: A file's text; below Tier 3, only inside logs/ and crash-reports/ (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-files-contents)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/files/copy`: Staff copy file (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-files-copy)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/files/decompress`: Staff decompress file (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-files-decompress)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/files/delete`: Staff delete files (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-files-delete)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/files/download`: One file, streamed; below Tier 3, only inside logs/ and crash-reports/ (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-files-download)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/files/list`: A directory; below Tier 3, only inside logs/ and crash-reports/ (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-files-list)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/files/mkdir`: Staff mkdir (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-files-mkdir)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/files/pull`: Staff pull file (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-files-pull)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/files/pull/status`: Staff pull status (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-files-pull-status)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/files/rename`: Staff rename files (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-files-rename)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/files/upload`: Staff upload files (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-files-upload)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/files/write`: Staff write file (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-files-write)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/heal-install`: Run the platform's install self-healing on one of this brand's servers (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-heal-install)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/install-log`: Staff install log (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-install-log)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/permissions`: Staff grantable permissions (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-permissions)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/power`: Staff power (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-power)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/reinstall`: Staff reinstall (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-reinstall)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/resources`: Staff resources (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-resources)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/retry-install`: Run the install again for a server in installfailed or stuck installing (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-retry-install)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/schedules`: Staff list schedules (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-schedules)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/schedules/{schedule_uuid}`: Staff get schedule (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-schedules-schedule-uuid)
- `DELETE /api/v1/orgs/{org_slug}/staff/servers/{uuid}/schedules/{schedule_uuid}`: Staff delete schedule (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-delete-api-v1-orgs-org-slug-staff-servers-uuid-schedules-schedule-uuid)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/schedules/{schedule_uuid}/execute`: Staff execute schedule (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-schedules-schedule-uuid-execute)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/schedules/{schedule_uuid}/runs`: Staff schedule runs (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-schedules-schedule-uuid-runs)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/schedules/{schedule_uuid}/toggle`: Pause a schedule that is hurting the server, or resume one (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-schedules-schedule-uuid-toggle)
- `PATCH /api/v1/orgs/{org_slug}/staff/servers/{uuid}/settings`: Staff patch settings (https://docs.coritan.com/api/reference/organizations/organizations-members/staff/#op-patch-api-v1-orgs-org-slug-staff-servers-uuid-settings)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/sleep`: Sleep and start-queue state of a free server; policy: none for a paid one (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-sleep)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/snapshots`: Staff list snapshots (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-snapshots)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/snapshots`: Staff create snapshot (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-snapshots)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/snapshots/estimate`: Staff snapshot estimate (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-snapshots-estimate)
- `DELETE /api/v1/orgs/{org_slug}/staff/servers/{uuid}/snapshots/{snapshot_uuid}`: Staff delete snapshot (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-delete-api-v1-orgs-org-slug-staff-servers-uuid-snapshots-snapshot-uuid)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/snapshots/{snapshot_uuid}/download`: Staff download snapshot (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-snapshots-snapshot-uuid-download)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/snapshots/{snapshot_uuid}/lock`: Staff toggle snapshot lock (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-snapshots-snapshot-uuid-lock)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/snapshots/{snapshot_uuid}/restore`: Staff restore snapshot (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-snapshots-snapshot-uuid-restore)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/software`: Staff installed software (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-software)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/software/catalog`: Staff software catalog (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-software-catalog)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/software/catalog/{key}/versions`: Staff software catalog versions (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-software-catalog-key-versions)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/software/change`: Staff change software (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-software-change)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/software/context`: Staff software context (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-software-context)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/software/installs`: Staff software installs (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-software-installs)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/software/installs/{install_uuid}/cancel`: Staff cancel install (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-software-installs-install-uuid-canc)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/software/installs/{install_uuid}/retry`: Staff retry install (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-software-installs-install-uuid-retr)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/startup`: How the server starts: runtime, command (override and default), variables (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-startup)
- `PATCH /api/v1/orgs/{org_slug}/staff/servers/{uuid}/startup`: Change the runtime, the startup command or the variables (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-patch-api-v1-orgs-org-slug-staff-servers-uuid-startup)
- `PATCH /api/v1/orgs/{org_slug}/staff/servers/{uuid}/startup-variables`: Staff patch startup variables (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-patch-api-v1-orgs-org-slug-staff-servers-uuid-startup-variables)
- `PATCH /api/v1/orgs/{org_slug}/staff/servers/{uuid}/subdomain`: Staff patch subdomain (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-patch-api-v1-orgs-org-slug-staff-servers-uuid-subdomain)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/users`: Staff list subusers (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-users)
- `PUT /api/v1/orgs/{org_slug}/staff/servers/{uuid}/users/{subuser_id}`: Staff update subuser (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-put-api-v1-orgs-org-slug-staff-servers-uuid-users-subuser-id)
- `DELETE /api/v1/orgs/{org_slug}/staff/servers/{uuid}/users/{subuser_id}`: Staff remove subuser (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-delete-api-v1-orgs-org-slug-staff-servers-uuid-users-subuser-id)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/wake`: Start a sleeping free server on the customer's behalf (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-wake)
- `POST /api/v1/orgs/{org_slug}/staff/servers/{uuid}/wake-queue/kick`: Staff kick wake (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-post-api-v1-orgs-org-slug-staff-servers-uuid-wake-queue-kick)
- `GET /api/v1/orgs/{org_slug}/staff/servers/{uuid}/websocket`: The live console (https://docs.coritan.com/api/reference/organizations/org-staff-containers/staff/#op-get-api-v1-orgs-org-slug-staff-servers-uuid-websocket)