---
title: "Place a freeze on the card account"
method: POST
path: "/customers/{customerID}/card_accounts/{cardAccountID}/freeze"
tags: ["Cards"]
---

# Place a freeze on the card account

`POST /customers/{customerID}/card_accounts/{cardAccountID}/freeze`

Place a freeze on the card account

## Path parameters

- `customerID` string, required — A UUID that uniquely identifies a resource
- `cardAccountID` string, required — A UUID that uniquely identifies a resource

## Headers

- `Idempotency-Key` string, required

## Request body

- PostCardFreezeInput
  - `initiator` 'developer' | 'customer', required — The party that initiated the freeze. A freeze can be initiated by either the customer or developer. Only one freeze per initiator can be active at a time. If a new freeze is initiated by the same party, it overwrites any existing freeze
  - `reason` 'lost_or_stolen' | 'suspicious_activity' | 'planned_inactivity' | 'suspected_fraud' | 'other', required — The reason of the freeze
  - `reason_detail` string — A more detailed reason for the freeze
  - `starting_at` string — An optional starting time in ISO8601 format. It defaults to the current date-time if unspecified
  - `ending_at` string — An optional ending time in ISO8601 format. If this ending time is not specified, the card account will stay frozen indefinitely until it gets unfrozen by another request

## Response `200`

The successfully placed freeze

- CardFreeze — Card freeze
  - `card_account_id` string, required — A UUID that uniquely identifies a resource
  - `initiator` 'developer' | 'customer', required — The party that initiated the freeze. A freeze can be initiated by either the customer or developer. Only one freeze per initiator can be active at a time. If a new freeze is initiated by the same party, it overwrites any existing freeze
  - `reason` 'lost_or_stolen' | 'suspicious_activity' | 'planned_inactivity' | 'suspected_fraud' | 'other', required — The reason of the freeze
  - `reason_detail` string — A more detailed reason for the freeze
  - `starting_at` string — The start time of the freeze, in ISO8601 format
  - `ending_at` string — The end time of the freeze, in ISO8601 format
  - `created_at` string, required — The creation time of the freeze, in ISO8601 format

## Other responses

- `400` — Request containing missing or invalid parameters.
- `401` — Missing or invalid API key
- `500` — Unexpected error. User may try and send the request again.

---

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