---
title: "Issuer Freeze"
method: GET
path: "/v1/compliance/issuer-freeze/{address}"
tags: ["compliance"]
---

# Issuer Freeze

`GET /v1/compliance/issuer-freeze/{address}`

## Request

- Base URL: `https://api.bitpoort.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.bitpoort.com/v1/compliance/issuer-freeze/{address}`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

Wave 3c (Studio desk, per the route-ownership ruling) — live stablecoin
issuer-freeze status: ``isBlacklisted`` view reads against our own node
(USDT capital-L ``isBlackListed`` + USDC). Param route — registers AFTER
every literal per the binding order rule; the literal head
(``/issuer-freeze/``) can never swallow ``/monitored``/``/retroactive``.
Not key-scoped (no per-customer data) — the auth gate is the middleware's
FORENSIC prefix + the dependency above.

## Path parameters

- `address` string, required

## Query parameters

- `chain` string

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/bitpoort/apis/bitpoort-api.md) · [All operations](https://skmtc.dev/bitpoort/apis/bitpoort-api/llms.txt) · [OpenAPI document](https://skmtc.dev/bitpoort/apis/bitpoort-api/revisions/1a51d8566777?raw)