---
title: "Create a new exposure"
method: POST
path: "/collateral_management/exposures"
tags: ["Collateral Management"]
---

# Create a new exposure

`POST /collateral_management/exposures`

Permissions required: **Manage Collateral Exposures** and **Read vault activity**

Creates a new exposure in the Collateral Management service.

## Headers

- `Api-Signature` string, required
- `Api-Timestamp` integer, required

## Request body

- CMCreateExposureRequest — The request payload for creating a new collateral exposure.
  - `assetTrackingConfig` CMExposureAssetTrackingConfig, required — CM Exposure Asset tracking config
    - `asset` CMAssetType, required — Asset symbol or ticker (e.g. BTC)
      - `assetType` string, required
      - `type` 'ANCHORAGECUSTODY' | 'EXTERNAL', required — The type of asset held in the Collateral Package. This can be either `ANCHORAGECUSTODY` for assets held in Anchorage custody, or `EXTERNAL` for assets held outside of Anchorage custody.
    - `liquidationPriority` integer, required — The priority order for liquidating this asset in the event of a default or margin call
    - `notes` string — Optional additional notes or comments about the asset tracking configuration
    - `priceSource` 'COINBASEPRO' | 'KRAKEN' | 'KAMINO' | 'BINANCE' — This field specifies the source from which the price information is derived
  - `clientReferenceId` string — A reference identifier provided by the client for this collateral exposure. For example: client’s internal loan ID
  - `collateralPackageID` string, required — ID of the collateral package (packageId)
  - `priceStrategy` 'DEFAULT' | 'BID' | 'ASK' | 'MID' | 'LAST', required — This field specifies the pricing strategy to be used for the collateral package. To be implemented in the future
  - `type` 'LOAN', required — Type of exposure

## Response `201`

Successfully created collateral exposure

- CMCreateExposureResponse
  - `exposureId` string, required

## Other responses

- `400` — Bad Request
- `401` — Unauthenticated
- `403` — Forbidden
- `422` — Unprocessable Entity
- `429` — Too Many Requests
- `500` — Internal Server Error

---

[API](https://skmtc.net/anchorage/apis/anchorage-digital-api-reference.md) · [All operations](https://skmtc.net/anchorage/apis/anchorage-digital-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/anchorage/anchorage-digital-api-reference/versions/166864b1ec6d/schema)