Account Mapping
Resolve a company and retrieve enriched employee profiles for a workspace.
Account Mapping resolves a company by domain or LinkedIn identifier, then asynchronously enriches the company mapping: the link between a company and its enriched employee profiles.
Use Account Mapping when you need to discover and retrieve people attached to a target account, including profile data such as name, position, LinkedIn URL, email, phone number, and location when available.
Endpoints authenticate with your workspace API key and paginate like the rest of the API — see Authentication and Pagination.
Workflow
- Enrich company mapping starts an asynchronous enrichment job and returns
202 Accepted. - List company mappings returns paginated materialized mappings without profiles.
- Get company mapping returns one mapping with all enriched employee profiles.
Versioning and paths
Account Mapping endpoints are served under /api/v2. Other public Sillage API families may use a different version; this section documents only the Account Mapping endpoints listed here.
Endpoints
- List company mappings: paginated list of materialized mappings without profiles.
- Get company mapping: one mapping with enriched employee profiles.
- Enrich company mapping: asynchronous company resolution and enrichment.
Polling enrichment stage
After calling Enrich company mapping, poll the stage endpoint to track progress:
Use the request_id returned by the enrich response as the {id} path parameter.
Response shape
{
"id": 12345,
"type": "account_mapping",
"stage": "account_mapping_in_progress",
"created_at": "2026-06-12T08:30:00.000Z",
"updated_at": "2026-06-12T08:31:00.000Z",
"company": {
"id": 8421,
"name": "Acme",
"domain": "acme.com",
"linkedin_url": "https://www.linkedin.com/company/acme"
}
}Terminal stages: completed (enrichment succeeded) and account_mapping_failed (enrichment failed). Stop polling when either is reached.
Identifier caveat
Mapping, company, and profile IDs are numeric SQL identifiers from the current environment. They are not portable across environments.
For Get company mapping, use the top-level id returned by List company mappings. Do not use company.id or profiles[].id as mapping_id.