> For the complete documentation index, see [llms.txt](https://docs.b2copy.b2broker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2copy.b2broker.com/user-guide/view-your-account-details/requests-page-for-pamm-accounts-only.md).

# Requests page (for PAMM accounts only)

## For master accounts

On the **Requests** page of a PAMM master account, you can view a list of pending requests created by PAMM investors who are subscribed to the account, awaiting execution during the next rollover, as well as a list of executed requests.

PAMM traders have the option to execute individual or all pending requests by clicking Execute or Execute all requests. If there are multiple requests from the same investor, including an unsubscription request, the unsubscription request is prioritized during the rollover, and all other pending balance requests from that investor are automatically canceled.

<figure><img src="/files/ibhKmoGogfQs5LgGGMFM" alt="Requests page of a master account"><figcaption><p>Requests page of a master account</p></figcaption></figure>

## For investment accounts

On the **Requests** page of a PAMM investment account, you can view your pending requests, which are waiting for execution during the next rollover on the master account, as well as a list of executed requests. PAMM investors have the option to cancel pending requests by clicking **Cancel**. Once a request is canceled, its status is updated accordingly, and it is moved to the executed requests list.

<figure><img src="/files/H0gBmrtFLXJ4ObDlXw44" alt="Requests page of an investment account"><figcaption><p>Requests page of an investment account</p></figcaption></figure>

The following information is provided about each request:

**Ticket ID**

The request identifier.

***

**From**

The identifier of a client wallet from which funds are deposited or the number of the PAMM investment account from which funds are withdrawn.

***

**Type**

The request type. Possible types:

* **Deposit** – a request to transfer funds to a PAMM investment account that has already been subscribed to a PAMM master account
* ‍**Withdrawal** – a request to transfer funds from a PAMM investment account
* ‍**Unsubscribe** – a request to unsubscribe a PAMM investment account from a PAMM master account

***

**Created**

The date and time when a request was created.

***

**Execution Time**

The date and time when a request was executed.

***

**Currency**

The currency in which a deposit or withdrawal is requested.

***

**Amount**

The requested deposit or withdrawal amount.

***

**Status**

The request status. Possible statuses:

* **Pending** – a request awaits execution during the next rollover.
* ‍**Success** – a request was successfully executed.
* ‍**Partial** – a withdrawal request was partially executed because there were insufficient funds on a PAMM investment account for its full execution. In this case, the amount that was available on the account was withdrawn instead of the requested amount.
* ‍**Fail** – request execution failed.
* ‍**Cancelled** – a request was cancelled by a PAMM investor who submitted it.


---

# 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.b2copy.b2broker.com/user-guide/view-your-account-details/requests-page-for-pamm-accounts-only.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.
