---
title: "Withdraw unlock customer account"
method: POST
path: "/accounts/{zrn}/withdraw_unlock"
tags: ["Customer Accounts (MTA)"]
---

# Withdraw unlock customer account

`POST /accounts/{zrn}/withdraw_unlock`

Unlocks withdrawals for an existing customer account

## Path parameters

- `zrn` string, required

## Headers

- `X-SCX-SIGNED` string, required
- `X-SCX-TIMESTAMP` string, required

## Request body

- WithdrawUnlockCustomerAccountBody — Request body for withdraw-unlocking a customer account. Withdraw-unlocking an account removes the restriction on creating new withdrawal requests on the account. This is typically used to lift a withdraw-lock that was previously placed on an account as a precautionary measure when suspicious activity was detected, after the investigation has concluded and any issues have been resolved.

## Response `202`

Request to withdraw-unlock the customer account accepted. The withdraw unlock is applied asynchronously; clients should listen for the `customer_account_status_changed` webhook event to observe the new state.

- object — Empty JSON object.

## Other responses

- `400` — Bad Request
- `403` — Forbidden
- `404` — Not Found
- `500` — Internal Server Error
- `503` — Service Unavailable

---

[API](https://skmtc.net/zerohash/apis/zerohash-api.md) · [All operations](https://skmtc.net/zerohash/apis/zerohash-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/zerohash/zerohash-api/revisions/8b647d934363/schema)