> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/partner/what-would-you-like-to-learn-about/platform-features/marketing-content/requests/request-assets/check-asset-request-status.md).

# Check Asset Request Status

If you've requested content from a brand, you can check the status of your request on impact.com. Monitoring the status of your requests helps you track where each request is in its cycle and see the outcome once the brand has made a decision. A request can have one of the following statuses: *Open*, *Approved*, *Rejected*, or *Completed*.

## Understand statuses

* **Open:** Requests that the brand has received but have not yet been marked as *Rejected* or *Approved*.
* **Approved:** Requests that the brand has reviewed and marked as *Approved*.
* **Completed:** Requests that the brand has addressed and have added a final response to before closing them as *Completed*.
* **Rejected:** Requests that the brand has reviewed and marked as *Rejected*.

## Check request status

1. From the top navigation bar, select **Manage** → **More →** [**Requests**](https://app.impact.com/secure/mediapartner/ads/list-all-mp-ad-requests-flow.ihtml).
2. In the top-left-hand corner, use the following filters to further refine your request view:
   * **Brand** - Filter for requests you made to a specific brand.
   * **Request Type** - Filter by request type.
   * **Status** - Filter for **All** request statuses to view the complete list of requests.
3. Find the request you want to view the status of and check its **Status**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.impact.com/partner/what-would-you-like-to-learn-about/platform-features/marketing-content/requests/request-assets/check-asset-request-status.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.