Reo.dev: Reo Get Segment Accounts

List the accounts in a Reo.dev ACCOUNT segment: domain, developer activity band, customer fit, active developers, tech headcount and preferred technologies.

Tool ID: reo_get_segment_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.

import { Deepline } from 'deepline';

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

console.log(result.toolResponse.raw);

CLI

deepline run reo_get_segment_accounts --input '{
  "segment_id": "123e4567-e89b-42d3-a456-426614174000"
}'

Example response

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

{
  "data": {
    "data": [
      {
        "id": "id_123",
        "country": "US",
        "account_name": "Example"
      }
    ],
    "page_no": 123,
    "page_size": 123
  }
}

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

Input reference

Overview Returns the list of accounts belonging to a specific segment in your Reo workspace, with data (firmographics, activity, tags). Use the segment ID from List Segments to scope this call. ### Path Parameters | Name | Type | Required | Description | |---|---|---|---| | `segment_id` | string (UUID) | Yes | ID of an ACCOUNT-type segment, from List Segments | ### Errors | Code | When it happens | Response body | |---|---|---| | 400 | `X-API-KEY` header missing or empty | `{"error":"Missing API Key"}` | | 403 | Invalid API key, or a write API key used on this host · Segment ID doesn’t exist · Segment isn’t ACCOUNT type · Segment ID is malformed or empty | Bad key: `{"error":"Invalid API Key."}` · Unknown or wrong-type segment: `{"error":"Invalid Segment"}` · Malformed or empty ID: `{"error":"Invalid Segment Id."}` | ### ENUMs | Field | Value | Meaning | |---|---|---| | See the live schema below for the complete notes.

Name	Type	Required	Default	Details
`payload.segment_id`	`string`	Yes	—	ID of an ACCOUNT-type segment, from List Segments. Format: `uuid`.
`payload.page`	`integer`	No	`1`	Page number. Defaults to 1.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.data`	`array \| null`	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 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[].segment_id`	`string`	No	—	ID of the segment this record belongs to.
`result.data.data[].segment_name`	`string`	No	—	Display name of the segment.
`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[].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"`.
`result.data.data[].funding.total_investment_usd`	`string`	No	—	Total investment raised, in USD.

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

This output schema is too large for an inline display. Read the complete live contract with deepline describe reo_get_segment_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.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation