Team members

Import My Social Profile

Fill the key-holder's own record from a LinkedIn or Twitter profile.

The profile arrives in the body - nothing is fetched and no credit is spent. EMPTY fields are filled; values the person wrote are kept. Skills MERGE into expertise (capped at 15), up to three recent_posts are appended to the writing samples (ten kept), and a sent job_history REPLACES the stored one.

post/team-members/me/import-social

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/team-members/me/import-social
  • Auth: HTTP bearer

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

platform'linkedin' | 'twitter' required

Where the profile came from.

profile_urlstring required

Profile URL.

namestring nullable

Display name.

headlinestring nullable

LinkedIn headline or Twitter bio.

aboutstring nullable

Full bio / about section.

current_titlestring nullable

Current job title.

current_companystring nullable

Current company name.

avatar_urlstring nullable

Profile picture URL.

skillsstring[] nullable

Skills / expertise list.

recent_postsobject[] nullable

Recent posts, used as writing samples. Each needs text; scraped_at is optional. At most three are taken per call.

locationstring nullable

Location.

websitestring nullable

Personal website URL.

usernamestring nullable

Twitter username.

biostring nullable

Twitter bio.

followersstring nullable

Follower count.

followingstring nullable

Following count.

Response

Successful Response

dataOrgPayload required

An open envelope for a single role, team, member or account record.

Open on purpose. The app's own response models on this surface grow with the product - RoleResponse gained rep_limits and manages_role_slugs, TeamResponse gained channel counts and a campaign count - and a pinned mirror would SILENTLY DROP whatever it had not caught up on. A dropped permission in a role read is the worst possible kind of stale: it reads as "they do not have it".

Changes

No recorded changes to this operation across all 3 revisions of this API.