# Force-Unlock a Terraform Backend Workspace

Admin force-clears a Terraform Backend workspace lock (the workspace is the package identified by id). Idempotent — succeeds even if no lock is held. A reason is required and is recorded on the audit trail.

Endpoint: POST /har/api/v3/packages/{id}/terraform-backend/force-unlock
Version: 1.0
Security: x-api-key

## Query parameters:

  - `account_identifier` (string, required)
    Unique identifier for the Harness account.

## Path parameters:

  - `id` (string, required)

## Request fields (application/json):

  - `reason` (string, required)
    Why the lock is being force-cleared. Recorded in the audit log.

## Response 200 fields (application/json):

  - `data` (object, required)

  - `data.lockedBy` (string)
    The previous lock holder, if any.

  - `data.wasLocked` (boolean, required)
    Whether a lock was actually held before this call.

## Response default fields (application/json):

  - `error` (object, required)

  - `error.code` (string)
    For some errors that could be handled programmatically, a short string indicating the [error code](https://docs.stripe.com/error-codes) reported.

  - `error.message` (string)
    A human-readable message providing more details about the error. These messages can be shown to users.

  - `error.param` (string)
    If the error is parameter-specific, the parameter related to the error. For example, we can use this to display a message near the correct form field.

  - `error.type` (string, required)
    The type of error returned.
    Enum: "INVALID_REQUEST_ERROR", "AUTHENTICATION_ERROR", "PERMISSION_ERROR", "API_ERROR"