Reo.dev: Reo Get Account Details

Look up one account in your Reo.dev workspace by company domain or Reo account ID: developer activity, customer fit, funding, tech headcount and preferred.

Tool ID: reo_get_account_details

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_account_details',
  {
    "org_id": "123e4567-e89b-42d3-a456-426614174000"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline run reo_get_account_details --input '{
  "org_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"
    }
  }
}

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

Input reference

Overview Returns detailed profile fields for a single account, without needing a segment ID. Identify the account by either `org_id` or `domain`. ### Path Parameters None. ### Errors | Code | When it happens | Response body | |---|---|---| | 400 | `X-API-KEY` header missing or empty · Neither `org_id` nor `domain` sent, or `domain=` is empty · No account matches the domain · `org_id` is unknown or malformed | Missing key: `{"error":"Missing API Key"}` · No identifier: `{"error":"Either domain or org_id query param is required."}` · Unknown domain: `{"error":"No account matches the given identifier."}` · Bad org_id: `{"error":"Invalid Account Id."}` | | 403 | Invalid API key, or a write API key used on this host | `{"error":"Invalid API Key."}` | ### ENUMs | Field | Value | Meaning | |---|---|---| | developer_activity | `HIGH` | `activity_score_numeric` 60–100. Strong engagement, high See the live schema below for the complete notes.

Name	Type	Required	Default	Details
`payload.org_id`	`string`	No	—	Account ID. Required: One of `org_id` / `domain`. Format: `uuid`.
`payload.domain`	`string`	No	—	Core domain of the account, for example `reo.dev`. Required: One of `org_id` / `domain`.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.data`	`object`	No	—	The account. A single object, not an array.
`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.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"`.
`result.data.data.funding.total_investment_usd`	`string`	No	—	Total investment raised, in USD.
`result.data.data.funding.last_round_amount_usd`	`string`	No	—	Amount raised in the last round, in USD.

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

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