---
title: "POST /debug/channels/withdraw"
method: POST
path: "/debug/channels/withdraw"
tags: ["internal", "channel", "debug"]
---

# POST /debug/channels/withdraw

`POST /debug/channels/withdraw`

Get a channel_withdrawal transaction object

## Request body

- ChannelWithdrawTx
  - `channel_id` string, required — Base58Check encoded tagged pubkey
  - `to_id` string, required — Base58Check encoded tagged pubkey
  - `amount` integer, required
  - `ttl` integer
  - `fee` integer, required
  - `nonce` integer, required
  - `state_hash` string, required — Base58Check encoded tagged hash
  - `round` integer, required

## Response `200`

Successful operation

- UnsignedTx
  - `tx` string, required — Base64Check encoded tagged byte array

## Other responses

- `400` — Invalid transaction
- `503` — The node is temporarily unable to handle the request: either its request queues are saturated (overload protection) or it has not yet reached a stable mode. Overload protection is applied to every endpoint, so this response can be returned by any operation. The Retry-After header tells the client how long to back off before retrying.

## Changes

- **2026-07-27** `ca5dd7bf8408` — 1 info
  - added the non-success response with the status `503`

[Change history](https://skmtc.dev/aeternity/apis/aeternity-node/changes/debug/channels/withdraw/post.md)

---

[API](https://skmtc.dev/aeternity/apis/aeternity-node.md) · [All operations](https://skmtc.dev/aeternity/apis/aeternity-node/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/aeternity/aeternity-node/revisions/597a254980b2/schema)