> For the complete documentation index, see [llms.txt](https://developer.parvenu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.parvenu.io/manage-lists/list-saved-views.md).

# List Saved Views

List the saved views you can use. Send one as saved\_view on any list enrichment to run it on just that view's contacts.

<mark style="color:green;">`POST`</mark> `/list_saved_views`

{% hint style="info" %}
Listing your saved views is **free**. `credits_used` is always 0.
{% endhint %}

A saved view is a named set of leads-table filters (the View, the ICP, the search box and the filter rules) saved in the Parvenu app. This endpoint lists the saved views you can use.

To run a list enrichment on just the contacts in a view, send the view's `name` (any case) or its `id` as `saved_view` on any `_list` endpoint, for example [Find Email Address List Lookup](/enrichments/find-email-address/list-lookup.md).

{% hint style="info" %}
A view saved with **Share with my team** off is only shown to the person who saved it.
{% endhint %}

**Headers**

| Name         | Value              |
| ------------ | ------------------ |
| Content-Type | `application/json` |

**Body**

| Name       | Type   | Description                                                                                                                                       |
| ---------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| `api_key`  | string | Your API Key.                                                                                                                                     |
| `listname` | string | Optional. Only the saved views you can use on this list: the ones saved on it, plus the ones saved for any list. Leave it out to see all of them. |

**Response**

The views are under `saved_views`. `total` is how many were returned. See [Response Format](/getting-started/response-format.md) for the fields every endpoint returns.

| Field             | Type           | Description                                                                |
| ----------------- | -------------- | -------------------------------------------------------------------------- |
| `id`              | number         | The view's id. You can send it as `saved_view` (as text).                  |
| `name`            | string         | The view's name. Send it as `saved_view` (any case).                       |
| `list_name`       | string or null | The list it was saved on. `null` when it can be used on any list.          |
| `any_list`        | boolean        | `true` when the view can be used on every list.                            |
| `view`            | string         | The leads-table View it keeps, for example `all` or `verified`.            |
| `icp`             | string         | The ICP it keeps. `all` means no ICP rule.                                 |
| `search`          | string         | The search box text it keeps. Left out when there is none.                 |
| `share_with_team` | boolean        | `true` when your whole team can use it. `false` means only you can see it. |

**Example**

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

```json
{
  "api_key": "your_api_key",
  "listname": "Homebuilders - VP"
}
```

{% endtab %}

{% tab title="Output" %}

```json
{
  "status": "success",
  "saved_views": [
    {
      "id": 3,
      "name": "Not Marketing",
      "list_name": "Homebuilders - VP",
      "any_list": false,
      "view": "all",
      "icp": "all",
      "share_with_team": true
    },
    {
      "id": 7,
      "name": "Owners Only",
      "list_name": null,
      "any_list": true,
      "view": "verified",
      "icp": "all",
      "search": "owner",
      "share_with_team": false
    }
  ],
  "total": 2,
  "credits_used": 0,
  "success": true
}
```

{% endtab %}

{% tab title="Error" %}

```json
{
  "status": "error",
  "error": {
    "code": "not_found",
    "message": "No user found for the provided API key"
  },
  "success": false
}
```

{% endtab %}
{% endtabs %}

## Using a saved view on a list enrichment

Add `saved_view` to the body of any `_list` endpoint:

```json
{
  "api_key": "your_api_key",
  "listname": "Homebuilders - VP",
  "saved_view": "Not Marketing"
}
```

The run then reads only the contacts in that view. A few rules apply on every endpoint:

* **Don't mix it with your own row filters.** Sending `saved_view` together with a non-default `view`, a `filter_stack` or a `search` returns a 400: `Send saved_view, or view / filter_stack / search, not both.`
* **The view must be one you can use on that list.** A view that does not exist on the list, or that you cannot see, returns a 404.
* **Nothing is charged when the lookup fails.** If the saved view cannot be looked up, you get a 502 and nothing is queued or charged. Try again.
* The acknowledgement includes `saved_view` with the view's name, so you can see which view the run used.