Entities
Understanding the entity data structure and attributes in Linkt
Entities are the core data objects in Linkt—companies and contacts discovered and enriched through your research workflows.
Overview
An entity represents a single record in a sheet. Each entity contains:
- Identity fields - Unique identifier and relationships
- Data - Attributes containing researched information
Entities are created when:
- A search workflow discovers new companies or contacts
- You import data via CSV ingest
- Contacts are discovered for existing companies
Entity Structure
Top-Level Fields
| Field | Type | Description |
|---|---|---|
id | string | Unique entity identifier |
sheet_id | string | ID of the sheet containing this entity |
parent_id | string | ID of parent entity (for hierarchical relationships) |
data | object | Entity attributes (see below) |
created_at | datetime | When the entity was created |
updated_at | datetime | When the entity was last modified |
EntityAttribute Structure
Each field in the data object is an EntityAttribute with metadata about the value:
| Field | Type | Description |
|---|---|---|
value | any | The attribute value (string, number, object, etc.) |
references | array | Source URLs where this information was found |
created_at | datetime | When this attribute was first set |
updated_at | datetime | When this attribute was last modified |
Source References
The references array provides transparency into where Linkt found each piece of information. Use these to verify data accuracy or for compliance requirements.
Primitive Attribute Types
Basic attribute values can be:
| Type | Example | Description |
|---|---|---|
string | "Acme Corp" | Text values |
number | 45.5 | Decimal numbers |
integer | 150 | Whole numbers |
boolean | true | True/false values |
Complex Attribute Types
Some attributes contain structured objects as their value.
Location
Geographic location data with structured address components:
| Field | Type | Description |
|---|---|---|
street | string | Street address |
city | string | City name |
state | string | State or province |
country | string | Country name |
zip_code | string | Postal/ZIP code |
SocialMediaProfile
Links to social media profiles:
| Field | Type | Description |
|---|---|---|
platform | string | Social platform name (linkedin, x, instagram) |
url | string | Full profile URL |
CriteriaMatch
For ICP criteria verification, indicates whether the entity matches specific criteria:
| Field | Type | Description |
|---|---|---|
verified | boolean | Whether criteria was verified as matching |
reasoning | string | AI explanation of the match decision |
Entity Hierarchy
Entities can have parent-child relationships, enabling you to model organizational structures.
How Hierarchy Works
When you create an ICP with multiple entity targets (e.g., company + person), discovered people are linked to their parent company:
Example: Company with Contacts
Parent Company:
Child Contact:
Querying Hierarchies
To get all contacts for a company:
- Query entities with the company's sheet
- Filter by
parent_idequal to the company'sid
Entity Types and Hierarchy
Parent-child relationships only exist within the same sheet. Company entities have parent_id: null, while person entities reference their parent company.
Working with Entity Data
Accessing Attribute Values
When working with entity data in code, access the value field of each attribute:
Handling Missing Data
Not all entities will have all fields populated. Always check for field existence:
Custom Fields
Custom fields from your ICP's enrichment section appear in data alongside default fields:
Next Steps
- Sheets - Where entities are stored
- Custom Fields - Extending entity schemas
- ICPs - Defining what entities to discover
- API Reference - Complete entity endpoint documentation