> For the complete documentation index, see [llms.txt](https://developers.myperfit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.myperfit.com/monitoreo/listado-de-actividad.md).

# Listado de actividad

{% hint style="info" %}
La autenticación a utilizar en este recurso es la misma que se utiliza en [Contacts API](/contacts-api/autenticacion.md). Para obtener el API key de un usuario puedes revisar este artículo.
{% endhint %}

## /activity

<mark style="color:blue;">`GET`</mark> `https://api.myperfit.com/v2/:account/activity`

Devuelve un listado de los eventos utilizando los filtros indicados. La estructura de los objetos varía dependiendo del tipo de evento, como se indica en la sección Webhooks.

#### Path Parameters

| Name    | Type   | Description      |
| ------- | ------ | ---------------- |
| account | string | Nombre de cuenta |

#### Query Parameters

| Name                    | Type    | Description                                                                                                                                             |
| ----------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| filters.track\_type     | string  | Filtrado por tipo de evento, ej:  `track.mail.sent`, `track.mail.opened`, `track.mail.clicked`, ... Dejar vacío para recibir todo los tipos de eventos. |
| filters.batch\_id       | string  | Filtrado por batch de envío, ej: `myaccount_bulk_123`                                                                                                   |
| view                    | string  | Formato de salida: `full`(toda la info disponible), `default`(info básica) o `simple`(sólo email).                                                      |
| filters.timestamp.gtrel | string  | Fecha relativa de inicio de datos. Ej: `now-1h`, `now-5d`                                                                                               |
| filters.timestamp.gt    | boolean | Fecha absulta de inicio de datos. No puede indicarse en conjunto con gtrel. Ej: `2019-10-17T03:49:14Z`                                                  |
| q                       | string  | Dirección de email.                                                                                                                                     |

#### Headers

| Name           | Type   | Description                 |
| -------------- | ------ | --------------------------- |
| Authentication | string | API Key de cuenta en Perfit |

{% tabs %}
{% tab title="200 " %}

```javascript
{
    "paging": {
        "next": "",
        "total": 2,
        "results": 2
    },
    "data": [
        { ... },    
        { ... }        
    ],
}
```

{% endtab %}
{% endtabs %}

### Paginado

Para obtener las sucesivas páginas, se debe utilizar el link que aparece en `paging.next`. Si su contenido está vació significa que esa es la última págnia.


---

# 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://developers.myperfit.com/monitoreo/listado-de-actividad.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.