---
title: "Release the mailbox's `.mv2` memory file lock"
method: POST
path: "/v1/mailboxes/{mailbox_id}/memory/unlock"
tags: ["memory"]
---

# Release the mailbox's \`.mv2\` memory file lock

`POST /v1/mailboxes/{mailbox_id}/memory/unlock`

## Request

- Base URL: `https://mbag.ai/api`
- URL: `https://mbag.ai/api/v1/mailboxes/{mailbox_id}/memory/unlock`
- Auth: HTTP bearer

Unconditional — releases whatever lock is held (or is a no-op if none is), regardless of who acquired it.

## Path parameters

- `mailbox_id` integer, required

## Response `200`

Released (or was already unlocked). Empty body.

## Other responses

- `401`: Missing or invalid credential, raised by the `ApiKeyAuth` extractor (`backend/src/api_keys.rs`) before the handler runs: no `Authorization` header, a non-`Bearer` scheme, a key that doesn't hash-match any row, or a key whose status isn't `active`. A header that isn't valid UTF-8, has no scheme token, or has `Bearer` with no key value returns 400 with this same JSON shape instead of 401.
- `404`: Mailbox not found (or not owned by the caller). Plain-text body.
- `500`: Database error checking mailbox ownership or releasing the lock. Plain-text body.

---

[API](https://skmtc.dev/mailbuttons/apis/mailbuttons-agent-mail-api.md) · [All operations](https://skmtc.dev/mailbuttons/apis/mailbuttons-agent-mail-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mailbuttons/apis/mailbuttons-agent-mail-api/revisions/fe2761823978?raw)