Skip to main content
The Fetch Connections endpoint creates an async task to retrieve the 1st-degree LinkedIn connections of your team’s account. All parameters are optional, you can fetch all connections with pagination, or narrow the results with a keyword search.

Endpoint

Request Body

All fields are optional. Sending an empty body fetches the first page of all connections.
string
Filter connections by name (e.g., "John" returns connections whose name contains “John”)
string
Sort order for results. Pass "RECENTLY_ADDED" to get your most recent connections first. Omit for default LinkedIn sort order.
number
Pagination offset, the index to start from. Defaults to 0. Use in combination with count to page through large connection lists.
number
Number of connections to return per request. Defaults to 40, maximum 500. Larger pages mean fewer requests when pulling your full connection list.
To paginate through all your connections, keep incrementing start by the value of count until total in the response is less than count (or 0), which means you’ve reached the end.

Response

The endpoint returns immediately with a task ID. Connections are fetched asynchronously.
boolean
Whether the task was created successfully
string
UUID to poll for results via Get Task Status
string
Human-readable confirmation

Polling for Results

After creating the task, poll the Get Task Status endpoint until the status is completed:

Completed Response

When the task finishes, task_output contains the cleaned list of connections:

Code Examples

Error Responses

FAQ

Each connection object includes: name (full name), first_name, last_name, headline (job title / description), public_identifier (LinkedIn profile slug), entity_urn (LinkedIn person URN), and profile_image_url (profile picture URL or null). The public_identifier can be passed to Fetch Profile and the entity_urn can be passed to Send Message.
Use start and count together. Start with start: 0, count: 500, then start: 500, count: 500, and so on. When the total in a response is less than your requested count, you have reached the last page. Each request creates a separate async task.
Passing "RECENTLY_ADDED" as sort_type returns connections in reverse chronological order, your most recently connected people appear first. Omitting sort_type uses LinkedIn’s default relevance-based sort.
The connections belong to the LinkedIn account running the Chrome extension, specifically your team’s oldest admin member’s account. This is the same account used for actions like Like Post, Comment on Post, and Send Message.
Yes. Pass the entity_urn from a connection object directly to the Send Message endpoint as the recipient_urn field. Since connections are 1st-degree, messaging them will always succeed.
Most connection fetch tasks complete within seconds to a minute, depending on when the Chrome extension picks up the task. We recommend polling every 5 seconds with a timeout of 2-3 minutes.

Learn More