Endpoint
Request Body
LinkedIn profile URN for the invitee (a
urn:li:fsd_profile:... string).
You can also pass the URN without the urn:li:fsd_profile: prefix — the plugin will normalize it.Response
The endpoint returns immediately with a task ID:Whether the task was created successfully
UUID to poll for results via Get Task Status
Human-readable confirmation
Polling for Results
Poll the Get Task Status endpoint until the status iscompleted:
Completed Response
When the task finishes,task_output will include:
Code Examples
Error Responses
| Status | Error | Description |
|---|---|---|
400 | Missing or invalid 'profile_urn' | The profile_urn field is missing or not a string |
401 | Missing API Key / Invalid API Key | API key is missing or invalid |
403 | Plugin installation required... | No team member has an active Chrome extension. See Authentication |
404 | No admin user found in the team | Your team has no admin members |
FAQ
Who sends the connection request?
Who sends the connection request?
The connection request is executed from your team’s oldest admin member’s LinkedIn account (sorted by when they joined the team).
Can I include a custom message with the request?
Can I include a custom message with the request?
No. This endpoint only supports sending the connection invitation without an optional personalized message.
What is the correct profile URN format?
What is the correct profile URN format?
Use a LinkedIn
fsd_profile URN (for example: urn:li:fsd_profile:ACoA...).
If you omit the urn:li:fsd_profile: prefix, the plugin will normalize it automatically.Related
- Get Task Status - Poll for task results
- Fetch Profile - Get a profile URN for use as
profile_urn

