Get a member's entire profile, counts included, in one call
Returns a LinkedIn member's ENTIRE public profile in a single call, every section LinkedIn publishes. This is the lane for a one-call profile audit, and it replaces stacking /profile, /profile/complete, /profile/stats, the five /profile/interests/* lanes and /profile/similar. author is the same Author object /v1/linkedin/profile returns, with followers and following filled, plus verified, joined_at, ext.website, ext.is_influencer, ext.is_open_to_work, ext.is_hiring, ext.is_memorialized and ext.cover_url; verified is null on every other LinkedIn lane and real here. background holds summary (the About text), experiences, educations, skills, recommendations (received), current_position, top_education, certifications, honors, languages, projects, publications, volunteering, courses, patents, organizations, causes, top_skills, featured, interests and services. background.interests is bucketed into top_voices, companies, groups, schools and newsletters, the same five tabs the /v1/linkedin/profile/interests/* lanes sell separately. similar_profiles is LinkedIn's People-also-viewed rail, up to 20 members, which /v1/linkedin/profile/similar sells separately. background.experiences[] carries the skills tagged on each role, and background.skills[] carries endorsements plus endorsement_notes, none of which /profile/complete returns. THREE THINGS TO READ CAREFULLY. section_totals gives LinkedIn's own count for each section and it can EXCEED the array beside it, because long sections are truncated at source; trust section_totals for a count, never background.<section>.length. author.ext.followers_approximate is true when this source reported a rounded follower count instead of an exact one, which it does on large accounts; /v1/linkedin/profile returns the exact integer. background.skills[].endorsements_is_floor is true when LinkedIn published a "99+" style label instead of a number, so the count is a minimum. background.services is returned on this lane only, is passed through in the source's own shape, and is null for a member who publishes no services page, which is most members. background.given_recommendations is NOT returned: this source carries only what the member received, and an empty array would read as "none given"; use /v1/linkedin/profile/complete for those. Every top-level key of the original record is kept unchanged for compatibility.
Request
- Base URL: https://www.socialcrawl.dev/v1
- URL: https://www.socialcrawl.dev/v1/linkedin/profile/all
- Auth: API key in header x-api-key
Query parameters
Full URL of the LinkedIn profile. (one of: url, urls; at least one required)
Up to 10 full LinkedIn profile URLs in one call, comma separated. The response becomes {items, total} instead of a single profile. Billed 5 credits per profile RETURNED, the same rate as a single call: duplicates are collapsed before the call and profiles that do not resolve are not charged, so a list with repeats or dead handles costs less than its length. A list where nothing resolves is a free 404. (one of: url, urls; at least one required)
Headers
Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.
Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.
Response
Successful response
Example response
{
"success": true,
"platform": "linkedin",
"endpoint": "/v1/linkedin/profile/all",
"credits_used": 1,
"credits_remaining": 4999,
"request_id": "req-abc123",
"idempotent_replay": true,
"meta": {
"hint": {
"code": "search_multi",
"message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
"method": "GET",
"path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
}
}
}Changes
No recorded changes to this operation across all 1 revision of this API.