Add connector(s) to the team
curl --request POST \
--url https://bee.theswarm.com/team/add-connector \
--header 'Content-Type: application/json' \
--header 'x-api-key: <api-key>' \
--data '
{
"linkedin_usernames": [
"<string>"
]
}
'{
"usernames_not_found": [
"<string>"
]
}Team Management
Add Connector
Add one or more LinkedIn profiles as connectors to your team.
POST
/
team
/
add-connector
Add connector(s) to the team
curl --request POST \
--url https://bee.theswarm.com/team/add-connector \
--header 'Content-Type: application/json' \
--header 'x-api-key: <api-key>' \
--data '
{
"linkedin_usernames": [
"<string>"
]
}
'{
"usernames_not_found": [
"<string>"
]
}Adds LinkedIn profiles as connectors to your team. A single request can include multiple usernames, making it efficient to onboard connectors in bulk.
Connectors are the team members whose LinkedIn connections form your searchable network. The more connectors you have, the broader your network coverage.
For a conceptual overview, see Team Management — Add Connector.
Omit the parameter to add connectors without a group assignment.
Omitting the header adds connectors to the team associated with your API key. The
Processing
Connector mapping happens asynchronously after the request is accepted. A 202 response means the job was queued successfully — mapping typically completes within seconds but may take a few minutes for profiles with large connection networks. A 200 response means the request was processed but no new connectors were queued (all provided usernames already exist in the team or none were found). If a username already exists as a connector in the team, it is silently skipped — no duplicate is created and the overall response remains 202.Groups
The optionalgroup parameter categorizes connectors within your team. All connectors in a single request receive the same assignment.
| Value | Use for |
|---|---|
employees | Current or former employees of your organization |
investors | Investors in your organization |
customers | Customers |
portfolio | Portfolio companies |
advisors | Advisors |
others | Any other relationship type |
Partner teams
Use thex-authenticate-team header to add connectors to a specific child team:
x-authenticate-team: <child_team_id>
child_team_id is returned when you create a child team.Authorizations
Body
application/json
LinkedIn URL slugs of the users to add as connectors. Accepts both username-only slugs (e.g. john-doe) and full profile URLs (e.g. https://linkedin.com/in/john-doe).
Member group to assign to the connector
Available options:
others, employees, investors, customers, portfolio, advisors Response
Request processed; no connectors were queued (all slugs resolved to existing members or none found)
LinkedIn URL slugs that were not found
Was this page helpful?
⌘I

