> ## 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.

# List the BMC's IPMI accounts

> Owner only — team members get 404, the same as a stranger. Lists the BMC's accounts by name and privilege; TenantOS
never returns BMC passwords. `host` is always null because TenantOS doesn't expose the BMC address. Needs a manageable
billing status. Any failure after the access checks (TenantOS unreachable or otherwise) answers 502.



## OpenAPI

````yaml /api-reference/openapi.yaml get /v1/dedicated/{id}/ipmi
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}/ipmi:
    parameters:
      - name: id
        in: path
        required: true
        description: The dedicated server's service id.
        schema:
          type: string
          format: uuid
    get:
      tags:
        - Dedicated
      summary: List the BMC's IPMI accounts
      description: >-
        Owner only — team members get 404, the same as a stranger. Lists the
        BMC's accounts by name and privilege; TenantOS

        never returns BMC passwords. `host` is always null because TenantOS
        doesn't expose the BMC address. Needs a manageable

        billing status. Any failure after the access checks (TenantOS
        unreachable or otherwise) answers 502.
      operationId: publicDedicatedListIpmiUsers
      responses:
        '200':
          description: The BMC accounts.
          content:
            application/json:
              schema:
                type: object
                required:
                  - success
                  - data
                properties:
                  success:
                    type: boolean
                    const: true
                  data:
                    type: object
                    required:
                      - host
                      - users
                      - hasCustomerAccount
                    properties:
                      host:
                        type: 'null'
                      users:
                        type: array
                        items:
                          $ref: '#/components/schemas/PublicDedicatedBmcUser'
                      hasCustomerAccount:
                        type: boolean
                        description: >-
                          Whether a `customer` account exists, i.e. whether a
                          reveal rotates it or creates it.
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '422':
          description: The service has no TenantOS id.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '502':
          description: The BMC couldn't be reached.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security:
        - bearerAuth: []
components:
  schemas:
    PublicDedicatedBmcUser:
      type: object
      required:
        - id
        - name
        - privilege
        - enabled
      properties:
        id:
          type: integer
        name:
          type: string
        privilege:
          type: string
          example: OPERATOR
        enabled:
          type: boolean
    ErrorResponse:
      type: object
      required:
        - success
        - error
      properties:
        success:
          type: boolean
          const: false
        error:
          type: string
          description: Human-readable error message.
      additionalProperties: true
  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'
  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.