---
title: "Authorize a settlement"
method: POST
path: "/atlas/settlements/{settlementId}/authorize"
tags: ["Atlas Settlement Network"]
---

# Authorize a settlement

`POST /atlas/settlements/{settlementId}/authorize`

Permissions required: **Authorize Settlements**


After your participant has proposed a settlement or accepted a settlement proposal, the details of the settlement must be authorized.

To authorize via API, the API key must have a special permission. Otherwise, authorization takes place in the app according to organization policy.

## Path parameters

- `settlementId` string, required

## Query parameters

- `participantId` string, required

## Headers

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

## Request body

- SNSettlementAuthorization
  - `acceptorId` string, required
  - `proposerId` string, required
  - `walletAmounts` SNWalletAmount[], required — In a proposal, each asset type can appear only once in the wallet amount list.
    - `assetType` string, required — A string representing a type of crypto-asset, which usually corresponds to the crypto asset's ticker symbol. Use `/asset-types` to list all of the supported asset types for your organization.
    - `quantity` string, required — The numeric value of this amount, excluding units. Use positive numbers for receiving and negative for sending assets. Amounts never include fees.
    - `walletId` string

## Response `200`

## Other responses

- `400` — Bad Request
- `401` — Unauthenticated
- `403` — Forbidden
- `404` — Not Found
- `409` — Conflict
- `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)