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

# Run a power action on many servers

> One power verb across up to 100 servers (cloud and dedicated mixed; duplicate ids are collapsed). Always 200 with one
result per id in the order sent — a server that can't be powered (not yours, suspended, pending, terminated, no graceful
shutdown on metal, unsupported by its BMC, already busy) is its own failed row, never a failed batch. Dedicated results
carry a `taskId` to watch; VM results are done when they come back. Requires operate access on each server.



## OpenAPI

````yaml /api-reference/openapi.yaml post /v1/services/power
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/services/power:
    post:
      tags:
        - Services
      summary: Run a power action on many servers
      description: >-
        One power verb across up to 100 servers (cloud and dedicated mixed;
        duplicate ids are collapsed). Always 200 with one

        result per id in the order sent — a server that can't be powered (not
        yours, suspended, pending, terminated, no graceful

        shutdown on metal, unsupported by its BMC, already busy) is its own
        failed row, never a failed batch. Dedicated results

        carry a `taskId` to watch; VM results are done when they come back.
        Requires operate access on each server.
      operationId: publicUserBulkPower
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - ids
                - action
              properties:
                ids:
                  $ref: '#/components/schemas/PublicUserServiceIds'
                action:
                  type: string
                  enum:
                    - start
                    - shutdown
                    - stop
                    - reboot
                    - reset
      responses:
        '200':
          description: Per-server results.
          content:
            application/json:
              schema:
                type: object
                required:
                  - success
                  - data
                properties:
                  success:
                    type: boolean
                    const: true
                  data:
                    type: object
                    required:
                      - action
                      - results
                    properties:
                      action:
                        type: string
                        enum:
                          - start
                          - shutdown
                          - stop
                          - reboot
                          - reset
                      results:
                        type: array
                        items:
                          type: object
                          required:
                            - id
                            - ok
                          properties:
                            id:
                              type: string
                            ok:
                              type: boolean
                            taskId:
                              type: string
                              description: Dedicated servers only — the task to watch.
                            error:
                              type: string
                              description: Customer-facing reason when ok is false.
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '500':
          $ref: '#/components/responses/ServerError'
      security:
        - bearerAuth: []
        - apiToken: []
components:
  schemas:
    PublicUserServiceIds:
      type: array
      description: Distinct service ids (duplicates are collapsed), 1–100 per request.
      minItems: 1
      maxItems: 100
      items:
        type: string
        minLength: 1
        maxLength: 64
    ErrorResponse:
      type: object
      required:
        - success
        - error
      properties:
        success:
          type: boolean
          const: false
        error:
          type: string
          description: Human-readable error message.
      additionalProperties: true
  responses:
    BadRequest:
      description: Validation failed or the request is malformed.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    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'
    ServerError:
      description: Unexpected server error.
      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.