> ## Documentation Index
> Fetch the complete documentation index at: https://docs.server.express/llms.txt
> Use this file to discover all available pages before exploring further.

# Reveal the server's root password

> The root (or Administrator, on Windows) password we set at order time or on the last reinstall. `password` is null
when we never set one. Needs operate access and a manageable billing status. Refused with 409 while a reinstall is
running, since the stored password belongs to the OS being wiped. Every reveal writes a CREDENTIALS_VIEW audit entry,
which shows on the activity tab.



## OpenAPI

````yaml /api-reference/openapi.yaml get /v1/dedicated/{id}/credentials
openapi: 3.1.0
info:
  title: Server.Express API
  version: 1.0.0
  description: >-
    The customer-facing Server.Express API: auth, billing, tickets, cloud and
    dedicated servers, hosting, reselling and account management. Every response
    uses the `{ success, data | error }` envelope.
  contact:
    name: Server.Express
    url: https://server.express
servers:
  - url: https://my.server.express/api
    description: Production
security:
  - bearerAuth: []
  - apiToken: []
tags:
  - name: API Tokens
  - name: Account
  - name: Auth
  - name: Cloud
  - name: Coupons
  - name: Credits
  - name: Dashboard
  - name: Dedicated
  - name: Health
  - name: Hosting
  - name: Integrations
  - name: Invoices
  - name: Livechat
  - name: Notifications
  - name: Passkeys
  - name: Payments
  - name: Products
  - name: Public
  - name: Public Invoices
  - name: Public Tools
  - name: Reseller
  - name: SSH Keys
  - name: Services
  - name: Tasks
  - name: Teams
  - name: Tickets
  - name: Web Hosting
  - name: Webhooks
paths:
  /v1/dedicated/{id}/credentials:
    parameters:
      - name: id
        in: path
        required: true
        description: The dedicated server's service id.
        schema:
          type: string
          format: uuid
    get:
      tags:
        - Dedicated
      summary: Reveal the server's root password
      description: >-
        The root (or Administrator, on Windows) password we set at order time or
        on the last reinstall. `password` is null

        when we never set one. Needs operate access and a manageable billing
        status. Refused with 409 while a reinstall is

        running, since the stored password belongs to the OS being wiped. Every
        reveal writes a CREDENTIALS_VIEW audit entry,

        which shows on the activity tab.
      operationId: publicDedicatedGetCredentials
      responses:
        '200':
          description: The login.
          content:
            application/json:
              schema:
                type: object
                required:
                  - success
                  - data
                properties:
                  success:
                    type: boolean
                    const: true
                  data:
                    type: object
                    required:
                      - username
                      - password
                    properties:
                      username:
                        type: string
                        enum:
                          - root
                          - Administrator
                      password:
                        type:
                          - string
                          - 'null'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '409':
          description: A reinstall is running on this server.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PublicDedicatedBusyError'
        '500':
          $ref: '#/components/responses/ServerError'
      security:
        - bearerAuth: []
        - apiToken: []
components:
  responses:
    Unauthorized:
      description: Missing, invalid or expired credentials.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    Forbidden:
      description: >-
        Authenticated but not allowed (missing scope, not an admin, or not your
        resource).
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    NotFound:
      description: The resource doesn't exist or isn't visible to you.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    ServerError:
      description: Unexpected server error.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
  schemas:
    PublicDedicatedBusyError:
      description: Refused because a job is already running on the server.
      allOf:
        - $ref: '#/components/schemas/ErrorResponse'
        - type: object
          required:
            - data
          properties:
            data:
              type: object
              required:
                - taskId
              properties:
                taskId:
                  type:
                    - string
                    - 'null'
                  description: >-
                    Our task id for the running job, or null when it's a
                    TenantOS-side job.
    ErrorResponse:
      type: object
      required:
        - success
        - error
      properties:
        success:
          type: boolean
          const: false
        error:
          type: string
          description: Human-readable error message.
      additionalProperties: true
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        Session access token (JWT) from POST /v1/auth/login or /v1/auth/refresh.
        A session satisfies every API scope.
    apiToken:
      type: http
      scheme: bearer
      bearerFormat: se_live_<prefix>_<secret>
      description: >-
        Personal API token created under Settings → API tokens. Only routes
        guarded by verifyApiAuth accept it, and the token must carry the scope
        named in the operation's x-required-scope.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.