> For the complete documentation index, see [llms.txt](https://docs.hyperbeat.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperbeat.org/hyperbeat-staking/staking-api/withdrawal.md).

# Withdrawal

To withdraw delegated HYPE, the first step is to undelegate from the Hyperbeat X P2P validator. This will remove the HYPE from being actively delegated back to the staking balance.

1. Create an [undelegate request](https://docs.p2p.org/reference/hyperliquid-undelegate), [sign it and send it ](https://docs.p2p.org/docs/signing-transaction-hyperliquid)to the network.
   1. Undelegated balance will immediately be reflected in the staking account balance
2. Create a [withdrawal request](https://docs.p2p.org/reference/hyperliquid-withdraw), [sign it and send it](https://docs.p2p.org/docs/signing-transaction-hyperliquid) to the network.
   1. Transfers from spot to staking balance have a 7 day unstaking queue, which means that the tokens will be locked up during this period. You can check the pending withdrawals using the [get delegator balances](https://docs.p2p.org/reference/hyperliquid-info) endpoint.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hyperbeat.org/hyperbeat-staking/staking-api/withdrawal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.