> For the complete documentation index, see [llms.txt](https://doc.ecomm.api.tietoevry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ecomm.api.tietoevry.com/e-commerce-payment-gateway/sandbox-guide/merchant-portal-home-page/my-requests.md).

# My Requests

The My Requests section provides an overview of all actions submitted by the merchant that would typically require approval or review in a live production environment.

### What You Can Do

This menu allows you to:

* View a history of all configuration requests, such as:
  * Creating a new shop
  * Requesting additional payment methods, Accepted wallets and more
  * Updating shop details
* Monitor the status of each request:
  * In Live: *Pending*, *Approved*, or *Rejected*
  * In Sandbox: All requests are automatically approved

In the My Requests section, you can see:

* The type of request you submitted
* The timestamp showing *when* the request was made
* The current status of the request (auto-approved in Sandbox)

### Why It’s Shown in Sandbox

Even though Sandbox requests are approved instantly, this section is presented for the following reasons:

* Transparency – Helps merchants understand what has been requested and when
* Audit Trail – Keeps a record of all actions in a clear, trackable format


---

# 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://doc.ecomm.api.tietoevry.com/e-commerce-payment-gateway/sandbox-guide/merchant-portal-home-page/my-requests.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.