> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/integrations/input-sources/api-based-integration/lists-api.md).

# Lists API

Custom Lists in Reo.Dev allows Sales and Marketing teams to import, enrich, and segment accounts or developers using a CSV upload. But what if your data changes frequently, or you want to add new entries dynamically, without uploading a new file every time?

That’s where the **Lists API** comes in.

***

### Why Use the Lists API?

Unlike the CSV upload in the UI, which replaces the entire list, the **Lists API lets you add new accounts or developers to an existing list**—without starting from scratch.

**Key Advantage**:

* **Continuously update your lists** with new data.
* Avoid re-uploading or overwriting lists.

**Developer Docs:** <https://developers.reo.dev/#tag/List>

***

#### Where to Get Your API Key

To use the Lists API, your dev team will need a **Product Usage API Key**.

**Steps to find the API Key:**

1. Go to **Settings →Configurations**
2. Click **Configure** under the **API Keys** section.

{% hint style="info" %}
Note: Only users with Admin Role in Reo.Dev can access the API Keys
{% endhint %}

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FVfjoU2fOvt3pKTwbmkdV%2Fimage.png?alt=media&amp;token=aee97391-ed40-4cf2-b8a3-a11f281c2d33" alt=""><figcaption></figcaption></figure>

3. Copy the key under **Product Usage API**.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FcM0psjpJzXCV7dlhWc8E%2Fimage.png?alt=media&amp;token=cf572758-8e11-4d78-87c7-a81866edbd6e" alt=""><figcaption></figcaption></figure>

***

### What the API Can Do

The Lists API supports 3 main actions:

| **Action**        | **Description**                                                     |
| ----------------- | ------------------------------------------------------------------- |
| **Create a List** | Set up a new Account or Developer list, define custom columns       |
| **Get All Lists** | Retrieve all existing lists created via API                         |
| **Add to List**   | Append new accounts or developers to a list (key advantage over UI) |

***

#### Share This With Your Tech Team

If you'd like to start using the Lists API to keep your account or developer lists always up-to-date, here’s the full API documentation:

> **🔗 Developer Docs:** <https://developers.reo.dev/#tag/List>

Share this link with your developer team or RevOps engineer to explore implementation.


---

# 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://docs.reo.dev/integrations/input-sources/api-based-integration/lists-api.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.