Skip to main content
POST
/
collateral_management
/
exposures
Create a new exposure
curl --request POST \
  --url https://api.anchorage-staging.com/v2/collateral_management/exposures \
  --header 'Api-Access-Key: <api-key>' \
  --header 'Api-Signature: <api-signature>' \
  --header 'Api-Timestamp: <api-timestamp>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "assetTrackingConfig": {
    "asset": {
      "assetType": "<string>"
    },
    "liquidationPriority": 123,
    "notes": "<string>"
  },
  "collateralPackageID": "<string>",
  "type": "LOAN",
  "clientReferenceId": "<string>"
}
'
{
  "exposureId": "<string>"
}
Requires Api-Signature.

Authorizations

​
Api-Access-Key
string
header
required

An API key associated with a security role

Headers

​
Api-Signature
string
required

A hex-encoded Ed25519 signature of timestamp_epoch_seconds + uppercase(http_method) + request_path + request_body.

Construction example:

toHex(
  ed25519Sign(
    signing_key,
    '{}{}{}{}'.format(timestamp_epoch_seconds, toUpper(httpMethod), httpRequestPath, httpBody)
  )
)
Pattern: ^[0-9A-Fa-f]{128,160}$
​
Api-Timestamp
integer<int64>
required

Current timestamp, represented as unix epoch seconds

Body

application/json

The details for creating a new collateral exposure

The request payload for creating a new collateral exposure.

​
assetTrackingConfig
object
required

CM Exposure Asset tracking config

​
collateralPackageID
string
required

ID of the collateral package (packageId)

​
priceStrategy
enum<string>
required

This field specifies the pricing strategy to be used for the collateral package. To be implemented in the future

Available options:
DEFAULT,
BID,
ASK,
MID,
LAST
​
type
enum<string>
required

Type of exposure

Available options:
LOAN
​
clientReferenceId
string

A reference identifier provided by the client for this collateral exposure. For example: client’s internal loan ID

Response

Successfully created collateral exposure

​
exposureId
string
required