> 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/es/sobre-que-te-gustaria-aprender/platform-features/marketing-content/requests/requests-overview-for-partners.md).

# Resumen de solicitudes para partners

Este artículo ofrece una descripción general para ayudarte, como socio, a entender cómo crear y gestionar solicitudes. Entre los tipos de solicitudes disponibles se incluyen activos, valores de seguimiento o fondos de desarrollo de marketing. Crear y gestionar estas solicitudes de forma eficaz facilita la colaboración y ofrece una mayor visibilidad de las interacciones con las marcas, tanto en curso como finalizadas.

## Tipos de solicitudes disponibles

* **Activo** - Solicitudes de un [recurso creativo](https://help.impact.com/partner/es/sobre-que-te-gustaria-aprender/platform-features/marketing-content/requests/request-assets/submit-and-manage-asset-requests-as-a-partner.md), por ejemplo, *Solicitud de recurso de correo electrónico*, a una marca.
* **Fondos de desarrollo de marketing** - [Solicitudes de fondos](https://help.impact.com/partner/es/sobre-que-te-gustaria-aprender/platform-features/marketing-content/requests/submit-and-manage-marketing-development-fund-requests-as-a-partner.md) asignados por una marca para apoyar iniciativas de marketing.
* **Valor de seguimiento** - Solicitudes relacionadas con métricas de rendimiento, por ejemplo, [*Solicitud de código promocional*](https://help.impact.com/partner/es/sobre-que-te-gustaria-aprender/platform-features/marketing-content/promo-codes/view-and-request-promo-codes-as-a-partner.md), a una marca.

  <div data-with-frame="true"><figure><img src="https://4119967529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2FRam9LVAvDYxGNaWCkqTc%2FScreenshot%202026-05-22%20at%2018.02.51.png?alt=media&amp;token=95ce9faa-c486-4b87-9d8e-a4db2e90143d" alt="" width="563"><figcaption></figcaption></figure></div>

## Consultar los estados y gestionar las solicitudes

Una vez que hayas enviado una solicitud a una marca, [puedes consultar su estado](https://help.impact.com/partner/es/sobre-que-te-gustaria-aprender/platform-features/marketing-content/requests/request-assets/check-asset-request-status.md). Después de enviarla, el estado de la solicitud será **Abierta**. A continuación, la marca podrá **Aprobarla** o **Rechazarla** . Cuando la marca esté conforme con el resultado, marcará la solicitud como **Completada**. Al consultar una solicitud, también es posible que veas los detalles y los comentarios relacionados.


---

# 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/es/sobre-que-te-gustaria-aprender/platform-features/marketing-content/requests/requests-overview-for-partners.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.
