Servers API

Read your servers over the Servor API with a servers:read token — list every server in your team and fetch a single server's details.

Read the servers in your team over the API. Use these endpoints to build an inventory, feed your own dashboards, or look up a server's id before reading its command history. Everything here is read-only — adding and editing servers stays in the dashboard: add a server in Servor.

These endpoints require the servers:read scope.

get/v1/serversScope: servers:read

List servers

Example request

curl https://api.servor.app/v1/servers \
  -H "Authorization: Bearer sv_live_..."

Example response

[
  {
    "id": "uuid",
    "name": "web-01",
    "host": "203.0.113.10",
    "os": "debian",
    "tags": [
      "prod"
    ],
    "lastSeenAt": "2026-08-20T10:00:00.000Z",
    "createdAt": "2026-08-01T00:00:00.000Z"
  }
]

get/v1/servers/{id}Scope: servers:read

Get a server

Parameters

iduuidpath · required
The server id.

Example request

curl https://api.servor.app/v1/servers/:id \
  -H "Authorization: Bearer sv_live_..."

Example response

{
  "id": "uuid",
  "name": "web-01",
  "host": "203.0.113.10",
  "os": "debian",
  "tags": [
    "prod"
  ],
  "lastSeenAt": "2026-08-20T10:00:00.000Z",
  "createdAt": "2026-08-01T00:00:00.000Z"
}

What you get back

GET /v1/servers — the list of servers in your team.
GET /v1/servers/{id} — the details of a single server.

Example

curl https://api.servor.app/v1/servers \
  -H "Authorization: Bearer sv_live_..."

Take an id from that list to read one server:

curl https://api.servor.app/v1/servers/srv_123 \
  -H "Authorization: Bearer sv_live_..."

Notes

Responses never include SSH credentials or encrypted payloads.
To read the command history of a server, see the Commands API.
A 403 means your token is missing the servers:read scope; a 404 means the server id doesn't exist or isn't in your team. See errors.

Servers API

What you get back

Example

Notes

See also