LinkedIn Company People API
특정 회사를 소속으로 적어 둔 회원을 반환합니다. handle과 헤드라인, 지역, 프로필 사진, 팔로워 수가 담깁니다.
GET /v1/linkedin/company/peopleLinkedIn Company People API는 언제 쓰나요
company_id를 이미 갖고 있고 그 회사 직원을 볼 때 사용하세요. LinkedIn 전체를 조건으로 걸러야 하면 search/people을 쓰세요.
API 레퍼런스 영문 원문
Returns a paginated list of members who work at a company, with handle, headline, location, and member URN. Get the company_id from /v1/linkedin/company. Each page is 10 members. On a plain call author.followers is LinkedIn's rounded display bucket, and only on the rows that show one (flagged author.ext.followers_approximate: true), and author.following is null on every row. When the primary source is momentarily rate-limited on page 1, a second source answers that page with current members of the same company in a different order and with exact follower counts (author.ext.followers_approximate: false), and data._warnings says so; page 2 onwards always comes from the primary, so a member can repeat or be missed across that boundary. Send include=profile and every row is joined, in the same call, to the member's profile lookup (/v1/linkedin/profile): author.followers becomes the exact follower count and author.ext.followers_approximate reads false on every row the lookup filled, whether the row arrived with LinkedIn's rounded bucket or with no count at all, author.following is filled with the member's connection count (on LinkedIn a member's following is the number of connections), and the location, the joined date (author.joined_at), and the country, website, cover image and profile flags on author.ext land where the row lacks them. Cost: 10 credits for the list; include=profile holds 4 credits per row and keeps only the rows filled from a fresh lookup, so a call costs at most 50; rows already in cache are free and unfilled rows are refunded. Pass limit (1 to 10) to join only the top rows: limit=3&include=profile costs at most 22. Time: the lookups run in parallel, about 1 second for 10 rows, up to 3 on a slow second, and never more than 8 seconds. The response carries a hydration block itemising rows, lookups, cache hits, credits and milliseconds.
75개 플랫폼을 병렬로 검색합니다
Company People API로 무엇을 할 수 있을까요
Company People 엔드포인트가 통합 스키마와 계산 필드를 담은 LinkedIn 데이터를 한 번의 요청으로 보내드려요. 스크래핑 인프라를 직접 만들거나 유지할 필요가 없어요.
요청 예시
# GET /v1/linkedin/company/people: Metered: holds 10 credits per page up front and refunds what the call does not use. Cache hits are free and failed calls are refunded.
# Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
# --max-time 47: this endpoint's measured p99 latency x 1.5.
# --retry 3: retries timeouts, 429 and 5xx, honoring Retry-After.
# -o response.json keeps only the final attempt's body.
# One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
# Next page: send pagination.next_cursor back as cursor until pagination.has_more is false.
IDEMPOTENCY_KEY=$(od -An -N16 -tx1 /dev/urandom | tr -d ' \n')
curl -sS --max-time 47 --retry 3 -o response.json \
-H "x-api-key: YOUR_API_KEY" \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
"https://www.socialcrawl.dev/v1/linkedin/company/people?company_id=1035" && cat response.json# GET /v1/linkedin/company/people: Metered: holds 10 credits per page up front and refunds what the call does not use. Cache hits are free and failed calls are refunded.
# Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
import os
import random
import time
import uuid
import requests
API_KEY = os.environ.get("SOCIALCRAWL_API_KEY", "YOUR_API_KEY")
TIMEOUT_S = 47 # this endpoint's measured p99 latency x 1.5.
MAX_RETRIES = 3
URL = "https://www.socialcrawl.dev/v1/linkedin/company/people"
def backoff(attempt):
# Exponential backoff with jitter: about 1 s, 2 s, then 4 s.
return 2 ** attempt * (0.5 + random.random() / 2)
def socialcrawl(params):
# One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
idempotency_key = str(uuid.uuid4())
for attempt in range(MAX_RETRIES + 1):
try:
res = requests.get(
URL,
params=params,
headers={"x-api-key": API_KEY, "Idempotency-Key": idempotency_key},
timeout=TIMEOUT_S,
)
body = res.json()
except (requests.RequestException, ValueError):
# A timeout, a dropped connection or a non-JSON gateway page: retry with the same key.
if attempt == MAX_RETRIES:
raise
time.sleep(backoff(attempt))
continue
if body["success"]:
return body
error = body["error"]
# Branch on error["type"], never on the message text.
if error["type"] == "RESOURCE_NOT_FOUND":
return None # refunded: nothing to read
retry_after = res.headers.get("Retry-After")
# SERVICE_UNAVAILABLE without Retry-After is a withdrawn endpoint: permanent.
permanent = error["type"] == "SERVICE_UNAVAILABLE" and retry_after is None
if not error.get("retryable") or permanent or attempt == MAX_RETRIES:
raise RuntimeError(f"{error['type']}: {error['message']} (request_id {body['request_id']})")
# Retry-After (seconds) wins; otherwise back off.
time.sleep(float(retry_after) if retry_after else backoff(attempt))
params = {
"company_id": "1035",
}
# Walk the list: send pagination.next_cursor back as cursor until has_more is false.
MAX_PAGES = 10 # each page is one call
items = []
for _ in range(MAX_PAGES):
body = socialcrawl(params)
if body is None:
break
items.extend(body["data"]["items"])
page = body.get("pagination") or {}
if not page.get("has_more") or not page.get("next_cursor"):
break
params["cursor"] = page["next_cursor"]
print(f"{len(items)} items")// GET /v1/linkedin/company/people: Metered: holds 10 credits per page up front and refunds what the call does not use. Cache hits are free and failed calls are refunded.
// Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
const API_KEY = process.env.SOCIALCRAWL_API_KEY ?? "YOUR_API_KEY";
const TIMEOUT_MS = 47_000; // this endpoint's measured p99 latency x 1.5.
const MAX_RETRIES = 3;
type Page = { next_cursor: string | null; has_more: boolean };
type SocialCrawlResponse =
| { success: true; data: any; pagination?: Page; credits_used: number; request_id: string }
| { success: false; error: { type: string; message: string; retryable: boolean }; request_id: string };
const sleep = (ms: number) => new Promise((resolve) => setTimeout(resolve, ms));
// Exponential backoff with jitter: about 1 s, 2 s, then 4 s.
const backoffMs = (attempt: number) => 2 ** attempt * 1000 * (0.5 + Math.random() / 2);
async function socialcrawl(url: URL) {
// One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
const idempotencyKey = crypto.randomUUID();
for (let attempt = 0; ; attempt++) {
let res: Response;
let body: SocialCrawlResponse;
try {
res = await fetch(url, {
headers: {
"x-api-key": API_KEY,
"Idempotency-Key": idempotencyKey,
},
signal: AbortSignal.timeout(TIMEOUT_MS),
});
body = (await res.json()) as SocialCrawlResponse;
} catch (error) {
// A timeout, a dropped connection or a non-JSON gateway page: retry with the same key.
if (attempt >= MAX_RETRIES) throw error;
await sleep(backoffMs(attempt));
continue;
}
if (body.success) return body;
// Branch on error.type, never on the message text.
if (body.error.type === "RESOURCE_NOT_FOUND") return null; // refunded: nothing to read
const retryAfter = res.headers.get("Retry-After");
// SERVICE_UNAVAILABLE without Retry-After is a withdrawn endpoint: permanent.
const permanent = body.error.type === "SERVICE_UNAVAILABLE" && retryAfter === null;
if (!body.error.retryable || permanent || attempt >= MAX_RETRIES) {
throw new Error(`${body.error.type}: ${body.error.message} (request_id ${body.request_id})`);
}
// Retry-After (seconds) wins; otherwise back off.
await sleep(retryAfter ? Number(retryAfter) * 1000 : backoffMs(attempt));
}
}
const url = new URL("https://www.socialcrawl.dev/v1/linkedin/company/people");
url.searchParams.set("company_id", "1035");
// Walk the list: send pagination.next_cursor back as cursor until has_more is false.
const MAX_PAGES = 10; // each page is one call
const items: unknown[] = [];
for (let page = 0; page < MAX_PAGES; page++) {
const body = await socialcrawl(url);
if (!body) break;
items.push(...body.data.items);
const next = body.pagination?.next_cursor;
if (!body.pagination?.has_more || !next) break;
url.searchParams.set("cursor", next);
}
console.log(`${items.length} items`);파라미터
| 파라미터 | 필수 | 설명 |
|---|---|---|
| company_id | 예 | LinkedIn numeric company ID (from /v1/linkedin/company). |
| page | 아니오 | Page number for pagination (default 1). |
| include | 아니오 | Set to `profile` (one token only) to join every row to the member's profile lookup in this one call: `author.followers` becomes the exact count and `author.ext.followers_approximate` reads false on every row the lookup filled, `author.following` is filled with the member's connection count, and the location, joined date, country, website, cover image and profile flags land where the row lacks them. Holds 4 credits per row and keeps only the rows filled from a fresh lookup; rows already in cache and rows that could not be filled are refunded, so a call costs at most 50 (10 + 4 per row) and the usual bill is lower. Adds about 1 second for 10 rows, up to 3 on a slow second and never more than 8, and nothing when the members are already cached; read `data.hydration` for the rows, the credits held and kept, and the time. (profile) |
| limit | 아니오 | Take the top N rows of this page (1 to 10). With `include=profile` it caps both the rows joined and the extra credits: `limit=3&include=profile` costs at most 22. The page cursor still advances past the full page of 10, so the rows past your limit are skipped, not carried to the next page. Without `include=profile` the call stays 10 credits. |
| max_pages | 아니오 | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| max_items | 아니오 | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| max_credits | 아니오 | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |
LinkedIn Company People API는 무엇을 돌려주나요
모든 응답은 하나의 통합 스키마를 따라요. 크레딧을 쓰기 전에 어떤 필드가 돌아오는지, 실제 응답 본문 그대로 확인해 보세요.
응답 예시 보기
{
"success": true,
"platform": "linkedin",
"endpoint": "/v1/linkedin/company/people",
"data": {
"items": [
{
"author": {
"id": "user_c6f330",
"username": "user_c6f330",
"display_name": "user_916d62",
"avatar_url": "https://example.com/avatars/user_7f671e.png",
"bio": "Sample comment text (redacted).",
"verified": true,
"followers": null,
"following": null,
"posts_count": null,
"likes_count": null,
"url": "https://example.com/user_c71750",
"location": null,
"ext": {
"urn": "user_ebb2b6",
"is_top_voice": false,
"is_premium": false,
"followers_approximate": null
}
}
},
{
"author": {
"id": "user_b74915",
"username": "user_b74915",
"display_name": "user_69038c",
"avatar_url": "https://example.com/avatars/user_e7645d.png",
"bio": "Sample comment text (redacted).",
"verified": true,
"followers": null,
"following": null,
"posts_count": null,
"likes_count": null,
"url": "https://example.com/user_5ba5e5",
"location": null,
"ext": {
"country": "US",
"country_name": "United States",
"urn": "user_415c82",
"is_top_voice": false,
"is_premium": false,
"followers_approximate": null
}
}
}
],
"total": 88418,
"dropped": 0
},
"credits_used": 10,
"request_id": "req_example000000",
"cached": false,
"pagination": {
"next_cursor": "sc.eyJ2IjoyLCJjIjoiMiIsImUiOiJsaW5rZWRpbi9jb21wYW55L3Blb3BsZSIsInAiOiJwYWdlIn0",
"has_more": true,
"page_size": 2,
"typical_page_size": null,
"next_page_credits": 10
},
"credits_remaining": 9999,
"source": "captured",
"captured_at": "2026-11-02T01:00:16.134Z",
"redacted": true
}통합 응답 구조를 보여 주는 실제 샘플이에요. 필드 값은 조회한 대상에 따라 달라져요.
LinkedIn Company People API는 어떻게 동작하나요
API 키와 함께 GET 요청을 보내면, 통합 스키마와 계산 필드를 담은 깔끔한 JSON이 돌아와요.
메서드
GET
응답 형식
JSON
소셜 미디어 데이터를 몇 초 만에 수집하는 방법
개발자를 위한 가장 빠른 소셜 미디어 스크래핑 API. 월간 활성 사용자 100억 명 이상을 포괄하는 75개 플랫폼에서 프로필, 게시물, 댓글, 분석 데이터를 수집하세요.
모든 플랫폼을 하나의 스키마로
동일한 응답 구조로 75개 플랫폼을 조회하세요. 연동은 한 번이면 충분합니다.
단순 수집을 넘어 계산된 필드 제공
엔드포인트가 해당 지표를 지원하고 계산에 필요한 원본 값이 있을 때, 정규화된 레코드에 engagement_rate, estimated_reach, content_category, language를 함께 담아 바로 활용할 수 있습니다.
코드 한 줄 쓰기 전에, 데이터부터
Visual Data Explorer에 URL만 붙여넣으면 결과 카드와 정형화된 테이블, CSV 내보내기를 바로 사용할 수 있습니다.
import requests
response = requests.get(
'https://www.socialcrawl.dev/v1/tiktok/profile',
params={'handle': 'charlidamelio'},
headers={'x-api-key': 'sc_YOUR_API_KEY'}
)
data = response.json(){
"success": true,
"platform": "tiktok",
"data": {
"author": {
"username": "charlidamelio",
"followers": 152400000
},
"engagement": {
"likes": 12400000000,
"engagement_rate": 0.087
},
"metadata": {
"language": "en",
"content_category": "lifestyle"
}
}
}자주 묻는 질문
API, 요금제, 기능에 대한 질문과 답변입니다.
문의하기LinkedIn 회사에 다니는 사람 목록은 어떻게 받나요?
직원 한 명당 어떤 필드를 주나요?
재직자의 팔로워 수도 받을 수 있나요?
직원 목록은 어떻게 페이지네이션하나요?
이 엔드포인트 요금은 얼마인가요?
여기 필요한 company_id는 어디서 얻나요?
인재 인텔리전스나 채용 용도로 쓸 수 있나요?
AI에게 SocialCrawl을 물어보세요
LinkedIn Company People 데이터, 가져올 준비 되셨어요?
API 키 받고 60초 안에 LinkedIn 데이터를 받아 가세요.
