Refresh Entity
API Reference
Refresh Entity
Re-run enrichments for an existing entity with optional shareholder recursion and rules engine β safe scope and preserve flags for name and profile data.
POST
Refresh Entity
Overview
Re-executes marketplace enrichments for an existing person or company, optionally:- Updates the entity display name and/or
entityDataprofile (opt-in with new flags) - Creates or re-enriches shareholders (companies,
depth> 0) - Runs the rules engine after enrichment completes
Backward compatibility: Requests that omit
refreshScope, preserveName, and preserveEntityData behave exactly as before: provider selection follows autoExecuteIntegrations, and the entity name is synced from normalized fullName when it changes. entityData is not modified unless you use refreshScope: "basic_data" with preserveEntityData.Endpoint
Authentication
Requires permission to execute enrichments (same asPOST /entities/{entityId}/enrich).
Path Parameters
UUID of the entity to refresh.
Request Body
Core options
When
true, bypass enrichment cache and call providers again.When
true, skip rules engine execution after enrichments complete.Shareholder / related-entity recursion depth (0β5). Ignored when
refreshScope is basic_data (always 0 β root entity only).Provider selection (legacy vs unified scope)
Legacy provider selection (used when
refreshScope is omitted):executeAllActiveEnrichments(boolean)enrichments(array of provider codes)enrichmentGroupRefs(array)excludeEnrichments(array)
POST /entities/automatic.Shareholder pipeline configuration (company dossiers,
depth > 0). Same shape as automatic creation.Optional unified scope. When set, it replaces
autoExecuteIntegrations for choosing root enrichments:| Value | Behavior |
|---|---|
basic_data | Single country-strategy basic-data provider (fresh call). Never processes shareholders. |
all_active | All active marketplace enrichments for the entity type and country. |
selected | Explicit list in providerCodes (required, non-empty). |
Required when
refreshScope is selected. Ignored otherwise.Safe field sync (opt-in)
Controls whether the root entity
name is updated after a successful enrichment:true: Keep the current name (recommended for manual review workflows).false: Sync name from provider mapping (basic_data) or normalizedfullName(other scopes).- Omitted (legacy): Sync name from normalized
fullNamewhen it differs β same as pre-2026-06-11 behavior.
Only applies when
refreshScope is basic_data and enrichment succeeded:- Omitted: Do not change
entityData(default / legacy). true: Gap-fill β merge provider-mapped profile intoentityDatawithout overwriting existing keys (fill empty fields only).false: Replace rootentityDatawith the provider-mapped profile from basic data.
all_active, selected, or legacy bodies without refreshScope: "basic_data".Example Requests
Legacy full refresh (unchanged behavior)
Safe basic-data refresh (name + profile preserved)
Basic data + gap-fill profile only
All active enrichments without renaming
Response β Success
skipRulesEngine is false, the response also includes rulesExecutionSummary at the root (same as Analyze Entity).
Real-time events
The API emits Socket.IO events on the organization channel:entity:refresh-startedentity:refreshed(on success)entity:refresh-failed(on fatal error)
Related endpoints
Execute enrichment
Run one or more specific providers without shareholder recursion.
Analyze entity
Rules engine only (optional enrich first).
Materialize relationships
Shareholder chain from normalized data.
Create automatic
Same enrichment + shareholder pipeline for new entities.