LINKEDIN_EXPERIENCE: LinkedIn User
A work experience entry for a LinkedIn user with role name, company, LinkedIn link, and date range.
Default definition. This article describes the default
LINKEDIN_EXPERIENCE definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches LINKEDIN_EXPERIENCE.Entity properties
| Property | Value |
|---|---|
| Entity code | LINKEDIN_EXPERIENCE |
| Display name | LinkedIn User |
| Plural | LinkedIn Users |
| Level | 100000 |
Use cases
Child entity of LINKEDIN_USER storing individual employment records. Three-column layout: experience (name with parentLink back to LINKEDIN_USER via comboKey), company details (company name, LinkedIn URL), and term (start/end dates as input fields rather than date type, suggesting raw LinkedIn data). Linked to parent via comboKey relationship.
Fields
Experience
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name |
linkedinUser | parentLink | LinkedIn User |
Company
| Field | Type | Required | Notes |
|---|---|---|---|
company_name | text | Company name | |
url | text (URL) | LinkedIn Link |
Term
| Field | Type | Required | Notes |
|---|---|---|---|
start_date | text | Start date | |
end_date | text | End date |
Relationships
- No declared relationships in the default definition.
Creating a LinkedIn User via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "LINKEDIN_EXPERIENCE",
"level": 100000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"company_name": "Example",
"url": "https://example.com",
"start_date": "Example"
}Listing LinkedIn Users records
# All linkedin users in your tenant
GET /v1/entities/LINKEDIN_EXPERIENCE/SUB