> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Reo.dev: Reo Get List Accounts

> List the accounts in a Reo.dev ACCOUNT list, with developer activity, customer fit and firmographics. Includes SDK V2 examples, schemas, and cost.

List the accounts in a Reo.dev ACCOUNT list, with developer activity, customer fit and firmographics.

> [!NOTE]
>
> Tool ID: `reo_get_list_accounts`

## Run this action

Use the TypeScript SDK for one call. Use `ctx.tools.execute(...)` inside a Play for durable calls, scheduled calls, or CSV processing.

```ts theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'reo_get_list_accounts',
  {
    "list_id": "123e4567-e89b-42d3-a456-426614174000"
  },
);

console.log(result.toolResponse.raw);
```

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline run reo_get_list_accounts --input '{
  "list_id": "123e4567-e89b-42d3-a456-426614174000"
}'
```

## Example response

The SDK returns this shape at `result.toolResponse.raw`. The example values illustrate the response.

```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
{
  "data": {
    "data": [
      {
        "id": "id_123",
        "country": "US",
        "account_name": "Example"
      }
    ],
    "page_no": 123,
    "page_size": 123
  }
}
```

Use `deepline describe reo_get_list_accounts --json` for the latest machine-readable contract.

## Input reference

### Overview Returns the list of accounts belonging to a specific list in your Reo workspace, with data (firmographics, technographics, funding etc). Use the list ID from **List of "Lists"** to scope this call. ### Path Parameters | Name | Type | Required | Description | |---|---|---|---| | `list_id` | string (UUID) | Yes | ID of an ACCOUNT-type list, from List of "Lists" | ### Errors | Code | When it happens | Response body | |---|---|---| | 400 | `X-API-KEY` header missing or empty · `page` isn't a positive integer (for example `page=abc`) | Missing key: `{"error":"Missing API Key"}` · Bad page: `{"error":"page must be a positive integer, got \"abc\""}` | | 403 | Invalid API key, or a write API key used on this host · List ID doesn't exist or is malformed · List isn't ACCOUNT type | Bad key: `{"error":"Invalid API Key."}` · Unknown or malformed list: `{"error":"Invalid List Id."}` · See the live schema below for the complete notes.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.list_id` | `string` | Yes | — | ID of an ACCOUNT-type list, from List of "Lists". Format: `uuid`. |
| `payload.page` | `integer` | No | `1` | Page number. Defaults to 1. Must be a positive integer. Minimum: 1. |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "### Overview Returns the list of accounts belonging to a specific list in your Reo workspace, with data (firmographics, technographics, funding etc). Use the list ID from **List of \"Lists\"** to scope this call. ### Path Parameters | Name | Type | Required | Description | |---|---|---|---| | `list_id` | string (UUID) | Yes | ID of an ACCOUNT-type list, from List of \"Lists\" | ### Errors | Code | When it happens | Response body | |---|---|---| | 400 | `X-API-KEY` header missing or empty · `page` isn't a positive integer (for example `page=abc`) | Missing key: `{\"error\":\"Missing API Key\"}` · Bad page: `{\"error\":\"page must be a positive integer, got \\\"abc\\\"\"}` | | 403 | Invalid API key, or a write API key used on this host · List ID doesn't exist or is malformed · List isn't ACCOUNT type | Bad key: `{\"error\":\"Invalid API Key.\"}` · Unknown or malformed list: `{\"error\":\"Invalid List Id.\"}` · Wrong-type list: `{\"error\":\"List is not an ACCOUNT type list.\"}` | ### ENUMs | Field | Value | Meaning | |---|---|---| | developer_activity | `HIGH` | `activity_score_numeric` 60–100. Strong engagement, high activity levels | | developer_activity | `MEDIUM` | `activity_score_numeric` 20–60. Moderate engagement, requires nurturing | | developer_activity | `LOW` | `activity_score_numeric` 0–20. Minimal activity, potential drop-off risk | | developer_activity | `\"\"` (empty) | No developer activity recorded for the account | | customer_fit | `STRONG` | Strong match to your ideal customer profile | | customer_fit | `MODERATE` | Partial match to your ideal customer profile | | customer_fit | `WEAK` | Weak match to your ideal customer profile | | employee_count_range | `1-10`, `11-50`, `51-250`, `251-1K`, `1K-5K`, `5K-10K`, `10K-50K`, `50K-100K`, `100K+` | Company headcount band | | agent_data | Dynamic | All the AI columns generated via agents corresponding to the accounts within the list will be available in this field | | user_input | Dynamic | All the columns imported during List Upload or CRM Upload corresponding to the accounts within the list will be available in this field | ### Things to Note - `id` is the account ID. It is the same value as `orgId` in `reo_account_link` and `account_id` in Get Account Activities and Get Deanonymised Developers. - A page past the last one returns 200 with `\"data\": []` (an empty array, unlike segment APIs which return `null`) and `page_size` `0`. Example: `{\"data\":[],\"page_no\":99999,\"page_size\":0,\"total_pages\":10}`. - Unlike segment APIs, an invalid `page` returns 400 here instead of falling back to page 1. - Accounts with no activity return `developer_activity` as `\"\"`, `first_activity` / `latest_activity` as `0`, and empty activity dates. - `first_activity` and `latest_activity` are epoch milliseconds. `tags` and `agent_tags` are comma-separated strings. `tech_stack` is an array.",
    "properties": {
      "list_id": {
        "type": "string",
        "description": "ID of an ACCOUNT-type list, from List of \"Lists\".",
        "format": "uuid"
      },
      "page": {
        "type": "integer",
        "description": "Page number. Defaults to 1. Must be a positive integer.",
        "default": 1,
        "minimum": 1
      }
    },
    "required": [
      "list_id"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `object` | Yes | — | Provider response payload. |
| `result.data.data` | `array` | No | — | Result records. |
| `result.data.data[].id` | `string` | No | — | Account ID. Same value as `orgId` in `reo_account_link`, and the `account_id` used by Get Account Activities and Get Deanonymised Developers. |
| `result.data.data[].country` | `string` | No | — | Country of the account's headquarters. |
| `result.data.data[].account_name` | `string` | No | — | Name of the account. |
| `result.data.data[].account_domain` | `string` | No | — | Core domain of the account. |
| `result.data.data[].active_developers_count` | `integer` | No | — | Count of active developers at the account in the last 30 days. |
| `result.data.data[].developer_activity` | `"HIGH" \| "MEDIUM" \| "LOW" \| ""` | No | — | Developer activity band for the account. See ENUMs. - `HIGH`: `activity_score_numeric` 60–100. Strong engagement, high activity levels - `MEDIUM`: `activity_score_numeric` 20–60. Moderate engagement, requires nurturing - `LOW`: `activity_score_numeric` 0–20. Minimal activity, potential drop-off risk - `""` (empty): No developer activity recorded for the account Allowed: `HIGH`, `MEDIUM`, `LOW`, \`\`. |
| `result.data.data[].customer_fit` | `"STRONG" \| "MODERATE" \| "WEAK"` | No | — | Customer fit score for the account, based on your ICP configuration. See ENUMs. - `STRONG`: Strong match to your ideal customer profile - `MODERATE`: Partial match to your ideal customer profile - `WEAK`: Weak match to your ideal customer profile Allowed: `STRONG`, `MODERATE`, `WEAK`. |
| `result.data.data[].first_activity_date` | `string` | No | — | Date of the first activity, `YYYY-MM-DD`. |
| `result.data.data[].last_activity_date` | `string` | No | — | Date of the latest activity, `YYYY-MM-DD`. |
| `result.data.data[].first_activity` | `integer` | No | — | First activity timestamp, epoch milliseconds. |
| `result.data.data[].latest_activity` | `integer` | No | — | Latest activity timestamp, epoch milliseconds. |
| `result.data.data[].tags` | `string` | No | — | Tags, as a comma-separated string. Empty string when none. |
| `result.data.data[].annual_revenue` | `string` | No | — | Estimated annual revenue. Returned as a string; format varies (for example `2B`, `$50M-$100M` or a raw number). |
| `result.data.data[].industry` | `string` | No | — | Industry classification of the account. |
| `result.data.data[].tech_functions_count` | `object` | No | — | Headcount by technology function at the account. |
| `result.data.data[].tech_functions_count.ai_ml_count` | `integer` | No | — | AI / ML headcount. |
| `result.data.data[].tech_functions_count.backend_engineering_count` | `integer` | No | — | Backend engineering headcount. |
| `result.data.data[].tech_functions_count.cloud_infrastructure_count` | `integer` | No | — | Cloud infrastructure headcount. |
| `result.data.data[].tech_functions_count.data_analytics_count` | `integer` | No | — | Data and analytics headcount. |
| `result.data.data[].tech_functions_count.devops_platform_reliability_count` | `integer` | No | — | DevOps, platform and reliability headcount. |
| `result.data.data[].tech_functions_count.engineering_count` | `integer` | No | — | General engineering headcount. |
| `result.data.data[].tech_functions_count.engineering_leadership_count` | `integer` | No | — | Engineering leadership headcount. |
| `result.data.data[].tech_functions_count.frontend_engineering_count` | `integer` | No | — | Frontend engineering headcount. |
| `result.data.data[].tech_functions_count.full_stack_count` | `integer` | No | — | Full-stack engineering headcount. |
| `result.data.data[].tech_functions_count.gtm_ops_corporate_count` | `integer` | No | — | GTM, operations and corporate headcount. |
| `result.data.data[].tech_functions_count.infrastructure_it_ops_count` | `integer` | No | — | Infrastructure and IT ops headcount. |
| `result.data.data[].tech_functions_count.innovation_rd_emerging_count` | `integer` | No | — | Innovation, R\&D and emerging tech headcount. |
| `result.data.data[].tech_functions_count.mobile_engineering_count` | `integer` | No | — | Mobile engineering headcount. |
| `result.data.data[].tech_functions_count.product_design_ux_count` | `integer` | No | — | Product, design and UX headcount. |
| `result.data.data[].tech_functions_count.program_delivery_agile_count` | `integer` | No | — | Program delivery and agile headcount. |
| `result.data.data[].tech_functions_count.qa_automation_testing_count` | `integer` | No | — | QA, automation and testing headcount. |
| `result.data.data[].tech_functions_count.security_compliance_count` | `integer` | No | — | Security and compliance headcount. |
| `result.data.data[].tech_functions_count.total_tech_employees` | `integer` | No | — | Total technical headcount. |
| `result.data.data[].tech_functions_count.unclassified_count` | `integer` | No | — | Headcount that couldn't be classified. |
| `result.data.data[].city` | `string` | No | — | City of the account's headquarters. |
| `result.data.data[].state` | `string` | No | — | State or region of the account's headquarters. |
| `result.data.data[].employee_count_range` | `"1-10" \| "11-50" \| "51-250" \| "251-1K" \| "1K-5K" \| "5K-10K" \| "10K-50K" \| "50K-100K" \| "100K+"` | No | — | Company headcount band. See ENUMs. - `1-10`, `11-50`, `51-250`, `251-1K`, `1K-5K`, `5K-10K`, `10K-50K`, `50K-100K`, `100K+`: Company headcount band Allowed: `1-10`, `11-50`, `51-250`, `251-1K`, `1K-5K`, `5K-10K`, `10K-50K`, `50K-100K`, `100K+`. |
| `result.data.data[].activity_score_numeric` | `number` | No | — | Numeric activity score, 0–100. Can be a decimal. |
| `result.data.data[].list_id` | `string` | No | — | ID of the list this record belongs to. |
| `result.data.data[].list_name` | `string` | No | — | Display name of the list. |
| `result.data.data[].developer_funnel` | `string` | No | — | Developer funnel stage of the account, for example `Exploring` or `Building`. |
| `result.data.data[].preferred_technology` | `string` | No | — | Preferred technologies, as a comma-separated string. |
| `result.data.data[].agent_tags` | `string` | No | — | Tags added by Reo Agents, as a comma-separated string. Empty string when none. |
| `result.data.data[].linkedin` | `string` | No | — | LinkedIn company page URL. |
| `result.data.data[].reo_account_link` | `string` | No | — | Deep link to the account in the Reo dashboard. |
| `result.data.data[].founded_year` | `string` | No | — | Year the company was founded, as a string. |
| `result.data.data[].tech_stack` | `array` | No | — | Technologies detected at the account. |
| `result.data.data[].funding` | `object` | No | — | Funding details. Every value is a string, never a number. An empty value can come back as `""` or the literal string `"null"`. |

The table shows the first 50 fields. Expand the raw schema below for every field.

> [!NOTE]
>
> This output schema is too large for an inline display. Read the complete live contract with `deepline describe reo_get_list_accounts --json`.

## Deepline cost

* Pricing model: `fixed` (per call).
* Estimated Deepline credits: `0` per pricing unit.
* Provider-native pricing may still exist outside Deepline credit billing.

## Related documentation

* [Connect integrations](https://deepline.com/docs/integrations.md)
* [SDK V2 quickstart](https://deepline.com/docs/sdk-v2/quickstart.md)
* [SDK reference](https://deepline.com/docs/sdk-v2/sdk-reference.md)
* [Run tools across a CSV](https://deepline.com/docs/sdk-v2/batch-csv.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.