Servor. docs
fr

Authentication

Authenticate to the Servor API with a Bearer token — create a token, send the Authorization header and verify it with GET /v1/me.

Every request authenticates with an API token sent as a Bearer header. There are no sessions and no cookies on the API.

curl https://api.servor.app/v1/me \
  -H "Authorization: Bearer sv_live_xxxxxxxxxxxx"

Getting a token

Create one in Settings → API tokens — see API tokens for the full walkthrough. The token is shown once at creation; store it in a secret manager. Live tokens are prefixed sv_live_.

Verifying your token

Call GET /v1/me to confirm the token works and see which team and scopes it carries:

{ "teamId": "…", "tokenId": "…", "scopes": ["servers:read", "incidents:write"] }

Keep tokens secret

A token acts on behalf of your team within its scopes. Never commit it or put it in client-side code. Revoke a leaked token immediately from API tokens.

Errors

A missing or invalid token returns 401. A valid token that lacks the required scope returns 403. See Errors for the full list.

See also