---
title: "Lock customer"
method: POST
path: "/participants/customers/{participant_code}/lock"
tags: ["Individual Participants"]
---

# Lock customer

`POST /participants/customers/{participant_code}/lock`

When platforms terminate a customer, they may alert zerohash through this endpoint.

## Path parameters

- `participant_code` string, required

## Headers

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

## Request body

- LockCustomersBody
  - `reason_code` 'user_request' | 'compliance_issue', required — Reason the customer is being locked.
  - `notes` string, required — Additional detail on the lock. Including useful context here can meaningfully speed up investigations on the zerohash side.

## Response `200`

Successfully locked customer.

## 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)