---
title: "Create a collect request"
method: POST
path: "/transactions/collect"
tags: ["Transactions"]
---

# Create a collect request

`POST /transactions/collect`

Permissions required: **Initiate Staking and Unstaking**



In staking, the "collect" operation is the action of claiming inactive unstaked amount back to
the available balance by moving them from the staking protocol or pool into a personal wallet. Once collected, these amounts are fully under wallet's owner control.

*NOTE: This endpoint is under development.*

## Headers

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

## Request body

- CreateCollectRequest
  - `amount` string — An amount of a crypto-asset to unstake, without units. The unit is derived from the asset type.
  - `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.
  - `description` string, nullable — An optional string providing more context to this transaction. It will be visible on the Anchorage Digital iOS app and will not be published to the blockchain.
  - `idempotentId` string — A client-provided unique ID for idempotent requests
  - `isFullAmount` boolean — Specifies whether to collect the full amount, which overrides any provided amount if set to true.
  - `source` SimpleSourceResourceDetails, required — An object representing a resource capable of sending funds. Construction example: ``` { "id":"1c920f4241b78a1d483a29f3c24b6c4c", "type":"WALLET" } ```
    - `id` string, required — The identifier of the resource
    - `type` 'WALLET', required — The type of the resource being referenced.
  - `stakingPositionId` string, required — Unique identifier of the staking position

## Response `201`

Successfully initiated a collect transaction

- CreateCollectResponse
  - `data` CreateStakeDetails, required
    - `transactionId` string, required — The transaction Id which can be used to reference this operation in other queries

## Other responses

- `400` — Bad Request
- `401` — Unauthenticated
- `403` — Forbidden
- `404` — Not Found
- `409` — Conflict
- `429` — Too Many Requests
- `500` — Internal Server Error
- `501` — Not Implemented 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)