> ## Documentation index
> Fetch the complete documentation index at: https://developer.rhombus.com/llms.txt
> Use it to discover all available pages before exploring further.

# Delete robot

> Remove the robot from the organization

```http
POST https://api2.rhombussystems.com/api/robot/delete
```

EU organizations send the same request to `https://api2.eu.rhombussystems.com`.

## Authentication and parameters

- `x-auth-apikey` (header, required): Your Rhombus API key. Must be accompanied by the `x-auth-scheme` header set to `api-token` (or `partner-api-token` for partner endpoints).
- `x-auth-scheme` (header, string, required, default: `api-token`): Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key. One of: `api-token`, `api`, `partner-api-token`, `partner-api`.

## Request body

Content type: `application/json`. Request to delete a robot device.

- `deviceUuid` (string<RUUID> | null, required): base 64 (url-safe) uuid string
- `mummify` (boolean | null, required): Whether to mummify the device instead of hard delete

## Response 200

OK. Content type: `application/json`

- `responseStatus` (string): Status of the unregister operation One of: `BASIC_AUTH_FAILED`, `PASSWORD_MISMATCH`, `SAME_PASSWORD`, `USER_EXISTS`, `USER_NOT_FOUND`, `DEVICE_NOT_FOUND`, `POLICY_NOT_FOUND`, `LOCATION_NOT_FOUND`, `ORG_NOT_FOUND`, `BAD_INPUT`, `SUCCESS`, `PASSWORD_TOO_SHORT`.

## OpenAPI

````yaml
openapi: 3.0.1
info:
  title: Rhombus API
  version: "1.0"
servers:
  - description: Production Server
    url: https://api2.rhombussystems.com
security:
  - ApiKeyAuth: []
paths:
  /api/robot/delete:
    post:
      description: Remove the robot from the organization
      operationId: deleteRobot
      parameters:
        - description: Authentication scheme identifier. Use `api-token` for standard API key authentication, `partner-api-token` for partner API key authentication. Must be paired with the `x-auth-apikey` header containing your API key.
          example: api-token
          in: header
          name: x-auth-scheme
          required: true
          schema:
            default: api-token
            enum:
              - api-token
              - api
              - partner-api-token
              - partner-api
            type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: "#/components/schemas/Robot_DeleteRobotWSRequest"
      responses:
        "200":
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Robot_DeleteRobotWSResponse"
          description: OK
      summary: Delete robot
      tags:
        - Robot Webservice
components:
  schemas:
    Robot_DeleteRobotWSRequest:
      description: Request to delete a robot device.
      properties:
        deviceUuid:
          description: base 64 (url-safe) uuid string
          example: AAAAAAAAAAAAAAAAAAAAAA
          format: RUUID
          nullable: true
          type: string
        mummify:
          description: Whether to mummify the device instead of hard delete
          example: false
          nullable: true
          type: boolean
      required:
        - deviceUuid
        - mummify
      type: object
    Robot_DeleteRobotWSResponse:
      description: Response from deleting a robot device.
      properties:
        responseStatus:
          $ref: "#/components/schemas/WebResponseStatusEnum"
      type: object
    WebResponseStatusEnum:
      description: Status of the unregister operation
      enum:
        - BASIC_AUTH_FAILED
        - PASSWORD_MISMATCH
        - SAME_PASSWORD
        - USER_EXISTS
        - USER_NOT_FOUND
        - DEVICE_NOT_FOUND
        - POLICY_NOT_FOUND
        - LOCATION_NOT_FOUND
        - ORG_NOT_FOUND
        - BAD_INPUT
        - SUCCESS
        - PASSWORD_TOO_SHORT
      type: string
  securitySchemes:
    ApiKeyAuth:
      description: Your Rhombus API key. Must be accompanied by the `x-auth-scheme` header set to `api-token` (or `partner-api-token` for partner endpoints).
      in: header
      name: x-auth-apikey
      type: apiKey
    oauth2:
      description: 'OAuth 2.0 authorization code flow with PKCE (`S256`). Send the access token as `Authorization: Bearer <token>`. Each operation lists the scopes it requires; a token without them is refused 403 with `WWW-Authenticate: Bearer error="insufficient_scope"`.'
      flows:
        authorizationCode:
          authorizationUrl: https://console.rhombus.com/oauth/authorize
          refreshUrl: https://auth-web.rhombussystems.com/oauth/token
          scopes:
            physical: Unlock doors and elevators, lockdown, alarms, speakers and robots
            read: View cameras, footage and settings
            write: Change settings and data
          tokenUrl: https://auth-web.rhombussystems.com/oauth/token
      type: oauth2
````