LinkedIn Company People (retired)

Retired. The upstream data provider withdrew the LinkedIn company employee directory, so this endpoint now always returns HTTP 410 and is never billed. Use POST /api/v1/linkedin/company instead: its featured_employees field returns a small sample (typically 4-6) of staff profiles.

POST/api/v1/linkedin/company/people

Authorizations

Authorizationstringheaderrequired

Bearer authentication header of the form Bearer <token>, where <token> is your Scavio API key (e.g. Bearer sk_live_your_key).

Body

application/json

companystring

Accepted but ignored; the endpoint always returns 410.

Example: microsoft

Request

curl -X POST 'https://api.scavio.dev/api/v1/linkedin/company/people' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer sk_live_your_key' \
  -d '{}'

# HTTP/1.1 410 Gone
# {"error":"This endpoint has been retired and is no longer available.",
#  "code":"endpoint_retired","reason":"The LinkedIn company employee directory was retired by the upstream provider."}

Response

"error": "This endpoint has been retired and is no longer available.",

"code": "endpoint_retired",

"reason": "The LinkedIn company employee directory was retired by the upstream provider.",

"alternative": "Use POST /api/v1/linkedin/company instead: its featured_employees field returns a small sample (typically 4-6) of staff profiles."

}

curl -X POST 'https://api.scavio.dev/api/v1/linkedin/company/people' \ -H 'Content-Type: application/json' \ -H 'Authorization: Bearer sk_live_your_key' \ -d '{}' # HTTP/1.1 410 Gone # {"error":"This endpoint has been retired and is no longer available.", # "code":"endpoint_retired","reason":"The LinkedIn company employee directory was retired by the upstream provider."}