---
title: "Force Unlock Sync Configuration"
method: POST
path: "/v1/buckets/{bucket_id}/syncs/{sync_config_id}/unlock"
tags: ["Bucket Syncs"]
---

# Force Unlock Sync Configuration

`POST /v1/buckets/{bucket_id}/syncs/{sync_config_id}/unlock`

## Request

- Base URL: `https://api.mixpeek.com`
- URL: `https://api.mixpeek.com/v1/buckets/{bucket_id}/syncs/{sync_config_id}/unlock`
- Auth: HTTP bearer and API key in header `X-Namespace`

Force-release a distributed lock on a sync configuration.

Use this when a sync trigger returns 'skipped_already_running' but no sync
is actually executing (zombie lock from a crashed worker).

## Path parameters

- `bucket_id` string, required
- `sync_config_id` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `422`: Unprocessable Entity
- `429`: Too Many Requests
- `500`: Internal Server Error
- `503`: Service Unavailable

## Changes

- **2026-10-09** `61a175e8eb9a`: 1 warning, 5 info
  - removed the optional property `detail` from the response with the `422` status
  - added the non-success response with the status `429`
  - added the non-success response with the status `503`
  - added the optional property `success` to the response with the `422` status
  - …2 more
- **2026-08-09** `5d4c905106b4`: 1 info
  - the endpoint scheme security `BearerAuth AND NamespaceHeader` was added to the API

[Operation history](https://skmtc.dev/mixpeek/apis/mixpeek-api/changes/v1/buckets/:bucket_id/syncs/:sync_config_id/unlock/post.md)

---

[API](https://skmtc.dev/mixpeek/apis/mixpeek-api.md) - [All operations](https://skmtc.dev/mixpeek/apis/mixpeek-api/llms.txt) - [OpenAPI document](https://skmtc.dev/mixpeek/apis/mixpeek-api/revisions/790bc16455f6?raw)