- “Get me the HR leadership at Apple”
- “Give me CHRO-type people at Apple”
- “CEO at StayVista”
naturalLanguage utterance (role, optionally at company). Arxena resolves synonyms and seniority server-side, maps std function/root/grade to LinkedIn Sales Navigator or Apollo filters when using those sources, then returns people plus a small resolved object. If the utterance has no company and you omit companyName / companyId / website, the API returns Please provide company name as well. A company name alone is resolved through companies ES → autocomplete → Google SERP domain → LinkedIn company id before search. A domain alone uses ES/autocomplete first, then Google {domain} linkedin company if that is only a stem guess.
One call (index)
Sales Navigator pipeline (Unipile pool)
Classifies the title → maps to Sales Navfunction IDs + seniority → searches via the shared Unipile Sales Navigator pool → post-filters by taxonomy.
Require one of:
| Source | Body fields |
|---|---|
| Shared Sales Nav pool | "dataSource": "pool" |
| Harvest Sales Nav | "dataSource": "harvest" |
| Explicit Unipile account | "dataSource": "unipile", "accountId": "..." |
resolved— std function / root / grade from the titlequery.appliedFilters— Sales NavfunctionIds+seniorities(or Apollo department/seniority whendataSource: "apollo")items— people after taxonomy post-filter
Apollo path
Same endpoint with"dataSource": "apollo". Taxonomy maps to person_department_or_subdepartments (including master_* roots) and person_seniorities.
What you see back
resolved— what the phrase became (function root × grade + confidence)items— filtered people at that company