Extract group members

Extract search-visible members matching a LinkedIn group ID.

POST /v1/actions/linkedin-extract-group-members/run/live

Authentication and cost

Use an API key in the Bearer header. This action costs 1 credit per returned record. The maximum result count is 100.

Request

bash

curl "$API_URL/v1/actions/linkedin-extract-group-members/run/live" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Idempotency-Key: unique-linkedin-extract-group-members-001" \
  -H "Content-Type: application/json" \
  -d '{
  "input": {
    "group_id": "123456"
  },
  "max_results": 10,
  "max_credits": 10
}'

Parameter	Requirement
`input.group_id`	Required non-empty string, at most 500 characters.
`max_results`	Integer from 1 to 100. Default 10.
`max_credits`	Optional positive integer; must cover the requested reservation.
`Idempotency-Key`	Required; 8–128 letters, numbers, underscores, hyphens, or colons.

Output fields

The response contains an output array. Available record fields include:

membership_status
linkedin_group_id
sales_navigator_profile_id
linkedin_profile_id
linkedin_profile_handle
linkedin_connection_degree
summary
first_name
last_name
full_name
linkedin_profile_url
linkedin_profile_picture
linkedin_people_post_search_url

Fields not available from the source are omitted. Your parser must tolerate absent properties and empty arrays. Examples are illustrative, not live customer data.

Completion and retries

Both 200 and 202 are valid responses. Read status: a live call can remain queued when capacity is busy. Poll the run until it reaches a terminal state. A terminal failed run can have HTTP 200; inspect its error and status, not just the HTTP code.

Reuse the same idempotency key and request body after a network timeout. A changed request under the same key returns 409.

Coverage notes

Extracts search-visible group members from the search index.

See coverage and limits before planning a production dependency. For async execution, replace /run/live with /run/async using the same input.